Repository navigation
docs(ci): note the Actions approval gate on the sync PR's own CI - #10
Merged
Merged
Conversation
Beyond the Allow-auto-merge repo setting, the bot-opened sync PR's own CI can sit at "action_required": GitHub gates pull_request-triggered check runs opened under the github-actions[bot] identity behind manual approval in the Actions tab, independent of auto-merge. Observed on run 31092673749 (PR #9) after #8 fixed the content-encoding bug the run had actually been failing on until then. No workflow-side retry resolves it; documenting it next to the auto-merge failure message so the next person hitting a stuck sync PR knows where to look.
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.
Summary
#8 fixed the actual content-encoding bug in the sync workflow; the subsequent run (31092673749) confirmed the fix works —
projects.jsoncommitted correctly and a sync PR (#9) opened — but then failed at the auto-merge step withAuto merge is not allowed for this repository, a pre-existing repo setting gap already documented in this repo's own CLAUDE.md.While chasing that, PR #9's own CI turned out stuck at
action_required: GitHub gatespull_request-triggered check runs opened under thegithub-actions[bot]identity behind manual approval in the Actions tab, independent of the auto-merge setting. Neither issue is fixable from inside the workflow script — both need a repository/organization setting change only an admin can make (Settings → General → Pull Requests → Allow auto-merge; Settings → Actions → General → workflow-run approval policy).This PR only adds documentation next to the existing auto-merge error message, so the next person (or agent) debugging a stuck sync run finds both causes in one place instead of re-diagnosing the second one from scratch.
Type of change
Checklist
pnpm check)Related issues
Follow-up to #6, #7, #8
Generated by Claude Code