Repository navigation
archify workflow hand-off at the pushed branch - #191
Merged
Merged
Conversation
GitHub Actions may not open pull requests in this repository, so the scheduled run on 2026-09-28 pushed archify/v3.0.0 and then failed at gh pr create. The workflow now pushes the branch, leaves a notice that links the compare page and exits 0. A later run that finds the branch unmerged repeats the notice. The pull-requests permission and GH_TOKEN are gone because nothing in the run calls gh. test/archify.test.mjs holds the workflow to that shape, and docs/archify.md tells the reader to open the PR by hand. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
The
archifyworkflow now ends at the pushed branch. Kyle chose this over enabling "Allow GitHub Actions to create and approve pull requests" in the repository settings.Cause
The scheduled run on 2026-09-28 (run 36435151786) vendored archify v3.0.0, pushed
archify/v3.0.0and failed atgh pr createwith "GitHub Actions is not permitted to create or approve pull requests". That release landed by hand in #178. The next scheduled run would have failed the same way on v3.0.1.Changes
.github/workflows/archify.ymldropsgh pr create. After the push it writes a notice on the run that links the compare page for the branch, and the job exits 0.archify/<tag>on the remote and the lock still behind repeats the notice. Before, it printed one log line.pull-requests: writeor setsGH_TOKEN. Nothing in the run callsgh.docs/archify.mdsays to open the PR by hand. A PR opened by a person starts thetestworkflow, so the close and reopen step is gone.test/archify.test.mjsgains one test that holds the workflow and the doc to this shape.Verification
gh pr createnode --test test/archify.test.mjs, aftercontents: writeonlygitstubbed, branch presentgitstubbed, branch absenttestworkflow on this PR, head3e7f067Post-merge check
Squash-merged as
d02ed08on 2026-09-28. Thetestworkflow on main passed at that commit with 696 of 696 tests, run 36514232922.A manual run of the
archifyworkflow on main (run 36514275158) finished green. It vendored v3.0.1, pushedarchify/v3.0.1and left this notice: "Pushed branch archify/v3.0.1; the archify gate passed in this run. Open the PR by hand", followed by the compare link. That branch has no PR yet.Branch
archify/v3.0.0was deleted from the remote after a check that main holds the same vendored tree.🤖 Generated with Claude Code