-
-
Notifications
You must be signed in to change notification settings - Fork 228
chore: add monthly flake.lock inputs update workflow #1978
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Conversation
771718f to
4e32d5b
Compare
acf3ba4 to
42b0c29
Compare
fa26b67 to
0131d17
Compare
19a20f1 to
7eee32d
Compare
WalkthroughAdds a GitHub Actions workflow that runs monthly and on-demand to checkout the repo, install Nix, obtain a GitHub App token, and run Mic92/update-flake-inputs to update the Nix Changes
Sequence Diagram(s)sequenceDiagram
participant Scheduler as Scheduler (cron / manual)
participant GH_Actions as GitHub Actions
participant Repo as Repository
participant NixAction as ephemeral-nix-action
participant GHApp as GitHub App Token Action
participant UpdateAction as Mic92/update-flake-inputs
Scheduler->>GH_Actions: trigger workflow
GH_Actions->>Repo: checkout code
GH_Actions->>NixAction: install ephemeral Nix
GH_Actions->>GHApp: generate GitHub App token (from secrets)
GH_Actions->>UpdateAction: run update-flake-inputs (with token, labels)
UpdateAction->>Repo: update flake.lock -> open PR
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Adds GitHub Action to automatically update
flake.lockevery Month. Uses Mic92/update-flake-inputs to create PRs with updated dependencies, preventing large, painful updates like the recent 2-year gap... #1714Targets develop branch with automated and dependencies labels. Can also be triggered manually via
workflow_dispatch.The workflow is configured with
GITHUB_TOKENwhich works but won't trigger CI workflows on the created pull requests (GitHub prevents this to avoid infinite loops).For CI workflows to run on the created PRs, you should set up a GitHub App:
APP_IDand private key asAPP_PRIVATE_KEYin repository secretsgithub-tokenstep to use the GitHub App tokenSee the full documentation for detailed instructions.
The current basic setup will work fine for creating PRs, the GitHub App is only needed if you want CI to automatically run on those PRs.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.