8c7b188ae5
Break the single job into four stages: `nix flake update`, checks, cachix, push to main. The benefit is that checks and cachix can use a matrix strategy in the future (to test / build for different OSes and nixpkgs releases). Also, the cachix build can run in parallel with checks. The downside is that we need to push to a temporary branch before we can run checks. Do that the simplest possible way (just hardcode the branch name).
39 lines
1.2 KiB
YAML
39 lines
1.2 KiB
YAML
# Copyright 2024 Google LLC
|
|
#
|
|
# Licensed under the Apache License, Version 2.0 (the "License");
|
|
# you may not use this file except in compliance with the License.
|
|
# You may obtain a copy of the License at
|
|
#
|
|
# http://www.apache.org/licenses/LICENSE-2.0
|
|
#
|
|
# Unless required by applicable law or agreed to in writing, software
|
|
# distributed under the License is distributed on an "AS IS" BASIS,
|
|
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
# See the License for the specific language governing permissions and
|
|
# limitations under the License.
|
|
|
|
name: nix flake update
|
|
|
|
on:
|
|
workflow_dispatch:
|
|
workflow_call:
|
|
|
|
jobs:
|
|
update:
|
|
runs-on: ubuntu-latest
|
|
permissions:
|
|
contents: "write"
|
|
steps:
|
|
- name: Check out repository
|
|
uses: actions/checkout@v4
|
|
with:
|
|
ref: main
|
|
- name: Install Nix
|
|
uses: DeterminateSystems/nix-installer-action@main
|
|
- name: Update and push flake.lock
|
|
run: |
|
|
git config user.email "github-actions[bot]@users.noreply.github.com"
|
|
git config user.name "github-actions[bot]"
|
|
git checkout -b flake-update
|
|
nix flake update --commit-lock-file
|
|
git push --force origin flake-update
|