feat(ci): give run-kipp-automation an optional stage input - #179
Merged
Conversation
Replace `phase: all | work | publish` with `stage: work | publish`, left unset when a single step runs the whole automation. The old enum collapsed two facts into one value: the shape of the run, and what this step does. `all` was not a peer of `work` and `publish` but their union, so the enum mixed levels and a reader had to already know the design to decode it. Naming only the second fact lets the first be derived, and leaves `phase` free to mean one thing: the module-facing value a two-function automation sees. The description also now gives the real reason for splitting. A refreshed token is the lesser one. The work stage holds a read-only token, so the write-scoped credential never co-exists with a model call. Declare the `record-digest` output that two-step workflows wire into their publish step, and drop the unused `ai-summary-model` input from setup-kipp.
Contributor
🛡️ SHA Pinned Actions Report✅ All 31 file(s) passed — actions are allowed and pinned as required. |
The `stage` description joined the two reasons with `and`, reading as though a split needed both. Either is sufficient on its own: a run that may outlive the hour an installation token is good for, or keeping the write-scoped token out of the step that calls a model.
pleb
enabled auto-merge
August 28, 2026 06:44
slewis74
approved these changes
Aug 28, 2026
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
2 participants
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.
What changed
run-kipp-automationtakesstage: work | publishinstead ofphase: all | work | publish. The input is optional, and leaving it unset means a single step runs the whole automation.Why
The old enum collapsed two different facts into one value:
allworkpublishallwas not a peer ofworkandpublishbut their union, so the enum mixed levels and a reader had to already know the design to decode it. Naming only the second fact lets the first be derived from it, and freesphaseto mean exactly one thing: the module-facing value a two-function automation sees inwork()andpublish().The input description also named token refresh as the only reason to split a run. It is one of two, and either is sufficient on its own: the run may outlive the hour an installation token is good for, or the split keeps the write-scoped token out of the step that calls a model, since the work stage holds a read-only token.
Also in this PR
run-kipp-automationdeclares therecord-digestoutput that generated two-step workflows wire into their publish step asKIPP_RUN_RECORD_DIGEST.setup-kippdrops the unusedai-summary-modelinput, along with its validation, step output andKIPP_AI_SUMMARY_MODELexport.Compatibility
Not a breaking change under the repository's versioning policy. Both Kipp actions landed in #177 and have never shipped in a tag or CHANGELOG entry, so nothing pinned to
v2.4.0,v2orlatestresolves to them. There are no callers in this repository, and the only known consumers are the Kipp plugin's workflow templates and its functional-testing sandbox, both updated in lockstep with this commit.Verification
The consuming side is updated and exercised against a live sandbox once this lands: the Kipp plugin re-pins to this commit, and the functional suite runs the two-step shape end to end (a
stage: workstep handing a digest-verified run record to astage: publishstep) plus the single-step shape.