Repository navigation
fix(promote): say in the job summary why GitHub refused a tag push - #217
Merged
Merged
Conversation
channel-tag.sh now captures a failed push's stderr and puts GitHub's own refusal lines on stdout, which Promote and Publish release add to the step summary. A denial to github-actions[bot] points at the App secrets; an App denial or a missing workflows permission points at the installation's permissions and a re-run for a fresh token. Unknown refusals are quoted without a hint. The 2026-10-27 failure was GitHub refusing the App's git access org-wide, not this workflow. Refs #215. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
azlekov
force-pushed
the
fix/promote-push-refusal-summary
branch
from
October 27, 2026 11:46
6e7c4af to
bdf04da
Compare
|
🎉 This PR is included in version 1.44.6 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Refs #215.
Why the Promote run failed
GitHub refused the App's git access across the org. The cause was not in this workflow.
dodi-smart-github-assistant[bot], notgithub-actions[bot], so-c http.https://github.com/.extraheader=did clear the credential thatactions/checkout@v7persists. Checkout v7 now keeps that header in a file pulled in throughincludeIf.gitdir. I checked locally with git 2.56: a bogus header in such a file is sent and gets a 401, and with the-creset no Authorization header goes out and the request gets a 200.v1from 1.30.0 to 1.39.5 and crossed 84 workflow and action files. The failed one would have crossed 69. A missing workflows permission also gives a different message ("refusing to allow a GitHub App to create or update workflow … withoutworkflowspermission"). This run got the generic "Permission to … denied".next. Other workflows' App tokens failed git fetch and push from about 21:50Z, and Promote failed at 07:28Z inside that window. The issue comments have the cross-repo evidence and the recovery after the installation's permissions were re-saved.What changes
push_taginscripts/channel-tag.shnow captures a failed push's stderr. It still writes that stderr to the log, and it also writes GitHub's refusal lines to stdout. Promote and Publish release already add stdout to the step summary. One hint follows:github-actions[bot]: set the App secrets.contents: write/workflows: writeand re-run for a fresh token. If a fresh token is also refused, an org owner re-saves the installation's permissions.The tests use a pre-receive hook on the test repository's bare remote to produce the refusals, so they check the real git output. Without the change the four new cases fail. With it, all 95 pass.
Not verified
No live push was made.
v1is correct at 1.44.5 and was not touched. #215 stays open until a real Promote moves the major tag with the App token. The next release will do that.🤖 Generated with Claude Code