feat(workflows): add reusable _update-flake-input workflow#20
Merged
Conversation
Reusable workflow_call target for bumping a single flake input and opening a squash-mergeable PR. Consumers (nix-ai, nix-darwin) call it via repository_dispatch when an upstream dryvist repo releases. - Inputs: input_name (required), runner_label (optional, RunsOn default) - Uses app token for push + PR creation; DeterminateSystems Nix action - No-op if flake.lock is unchanged; auto-merge enabled on created PR - input_name is channelled through env vars in run: steps to prevent shell injection from attacker-controlled client_payload fields Assisted-by: Claude:claude-opus-4-8
3 tasks
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
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.
Summary
Adds
_update-flake-input.yml— a reusableworkflow_calltarget that bumps a single flake input and opens a squash-mergeable PR in the calling repo.Part of the event-driven lock-propagation chain:
nix-claude-coderelease → dispatch →nix-ai→ dispatch →nix-darwin. This workflow is the shared implementation that both consumer repos call; the per-repo wiring (dispatch receivers) lands in separate PRs in each repo.Changes
.github/workflows/_update-flake-input.yml(new, reusable)workflow_callinputs:input_name(required),runner_label(optional)GH_APP_CLIENT_IDvar +GH_APP_PRIVATE_KEYsecret)DeterminateSystems/determinate-nix-actionfor Nix installnix flake update <input>→ no-op if unchanged, otherwisepeter-evans/create-pull-request+ auto-mergeinput_namereferences inrun:steps go through env vars (injection guard)Test plan
gh workflow run update-flake-input.yml --repo dryvist/nix-ai -f input_name=nix-claude-codecreates a lock-bump PR in nix-ai🤖 Generated with Claude Code