Most of the time we want to re-apply "manual"/"additional" commits from
the already open PR, however it is possible we may wish to run the CI
without doing so.
Add an on-by-default tickbox to toggle the `re_apply` step.
Instead of comparing the nixpkgs input revision, we can re-apply any
manually committed changes and then check if any files are different
before pushing.
Cancelling via `exit 1` will mark the workflow as "failed". Instead we
can write a `cancelled` step output and have all the following steps
be conditional.
This should help mitigate spammy force-pushes that don't actually update
the nixpkgs input.
This only affects _scheduled_ runs. Manually triggered updates will
always force-push to the update branch.
Split scheduling other branches into a dedicated workflow. The main
update workflow is no longer responsible for triggering the workflow on
_other_ branches.
Rather than interpolating input (flakeref & baseHref) into the build
expression, take advantage of `--argstr`.
See "Common evaluation options" in `nix build --help` for more detail.
We don't need to specify `/nixvim/` as part of our install path as that
is where gh-pages uploads to by default.
Rather, we only need to specify the full `/nixvim/foo/` in the base-href
and the install path should just be `/foo`.
We can no longer simply check the files list matches `[ flake.lock ]`,
since we now also touch `generated/` files.
Mergify conditions cannot be checked against "all" list items; checks
are always applied against "any" item. Therefore we need some
double-negatives to check that "any item does not match a regex that
does not match (flake.lock|generated/.*)".
Yes, this is horrible.
- Run the `update.yml` workflow on the triggered branch, replace the
job matrix with a conditional step that runs update on nixos-24.05.
- Added a `cancel-in-progress` concurrency group.
- Disabled committing in PR action (using negative add-paths).
- Rename workflow to simply "update"
- Drop the DeterminateSystems/update-flake-lock action
- Instead use `nix flake update --commit-lock-file`
- Also use `generate-files`'s `--commit` option
- Use peter-evans/create-pull-request to open a PR
