docs: note Workflows permission for bot GitHub App#10
Merged
Conversation
Two gotchas discovered while wiring CI for amcheste/overleaf-mcp: - The permissions table didn't list Workflows: Read & Write, but it's required for any push that creates or updates a file under .github/workflows/. GitHub rejects bot pushes that touch workflow files with a clear "refusing to allow a GitHub App ... without 'workflows' permission" message. Adding the entry to the canonical permissions table so future repo setups don't trip over it. - Changing an App's declared permissions is half the work; each existing installation also has to accept the new scope from Settings → Installations → Configure → Review permissions. Without that second click, the installation token issued at runtime still has the old scope and the workflow-push still fails with the same error. Both were learned the hard way today; documenting them so the next person setting up a new repo doesn't have to repeat the discovery. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
amcheste
approved these changes
Apr 25, 2026
Owner
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
Two gotchas discovered while setting up CI workflows in
amcheste/overleaf-mcp— both worth capturing in the canonical bot-account design doc so the next repo setup doesn't repeat the discovery:Workflows: Read & Writeis required for any push that creates or updates a file under.github/workflows/. The original permissions table only listed Contents, Pull requests, and Metadata. Without Workflows, GitHub rejects the push withrefusing to allow a GitHub App to create or update workflow ... without 'workflows' permission.Permission changes don't auto-propagate to existing installations. Updating the App's declared permissions is step one; the installation also has to accept the new scope from Settings → Installations → Configure → Review permissions. Without the second click, runtime tokens still have the old scope.
What changed
Both edits land in the same canonical place where someone setting up a new repo would already be looking.
Test plan
🤖 Generated with Claude Code