fix(ci): flake-sync opens auto-merge PR - #19
Merged
Conversation
main is protected (requires the test check), so the sync job's direct push would die at GH006 like the eval workflow did before #6. Push to a bot/ branch instead and open a PR that auto-merges once CI passes, using RELEASE_PAT so the PR actually triggers the required check. Add workflow_dispatch for manual runs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The flake-sync job ends with a direct push to main, but main is protected (requires the
testcheck), so the first run that detects drift will die at GH006 exactly as the eval workflow did before #6. All runs to date failed earlier at YAML validation (repaired in #5), so this latent failure has never been reached.This applies the #6 pattern: push the updated
flake.nixto abot/branch and open a PR that auto-merges once CI passes. Checkout and PR useRELEASE_PATso the sync PR triggers the requiredtestcheck;workflow_dispatchis added so the job can be run on demand. Loop prevention moves the[skip-flake-sync]marker into the PR title so the squash-merge commit carries it.Note:
flake.nixis currently stale on main. The fast-uri bump (#3) changedpackage-lock.jsonwhile this workflow was still failing validation, sonpmDepsHashno longer matches and the flake does not build. A dispatch run of this workflow after merge should detect the drift and open the sync PR that repairs it.