Commit an update to the CHaP flake input when the repo is deployed - #1397
Commit an update to the CHaP flake input when the repo is deployed#1397neilmayhew wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
Pull request overview
This PR aims to automatically keep the CHaP flake input lock up to date whenever the repo branch is updated during the deploy workflow, reducing the need for manual flake-lock bump interventions to keep downstream builds (e.g., Hydra) unblocked.
Changes:
- Adds a new “Update flake input” step to the
deployjob that updatesCHaPinflake.lockand pushes the result.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Unfortunately, the only way to test this is to merge it, and I doubt that it will work as-is. For example, I assume that it's not possible to push directly to Ideally, we'd allow direct pushes to So this PR is more about having a discussion than getting something merged right away. |
83f3700 to
a0343f8
Compare
|
We do have a weekly scheduled job to update
The problem with automatically generated PRs — even the ones that succeed — is that nobody seems to be looking at them. |
a0343f8 to
53ca85f
Compare
53ca85f to
8b1f51d
Compare
8b1f51d to
15810f7
Compare
The lock of the
CHaPflake input should be updated whenever therepobranch is updated, which happens in thedeployGitHub workflow step.This would avoid the need for manual interventions like #1396 to unbreak the Hydra build.