Skip to content

docs: correct the claim that the App needs Workflows write - #22

Merged
lucas-d-ramos merged 1 commit into
mainfrom
docs/correct-workflows-permission-claim
Aug 21, 2026
Merged

docs: correct the claim that the App needs Workflows write#22
lucas-d-ramos merged 1 commit into
mainfrom
docs/correct-workflows-permission-claim

Conversation

@lucas-d-ramos

Copy link
Copy Markdown
Contributor

v14.1.0 shipped an incorrect claim and it has already caused a problem.

The wrong claim

The reusable's header and the README both stated the App needs Workflows
(read/write)
, "not optional", because Dependabot's github-actions PRs edit
files under .github/workflows/.

Why it is wrong

The workflows permission governs pushing workflow files through the
Contents API. It does not gate merging a pull request that changes them.

Verified against this org — app/github-actions is itself an App token and
holds no workflows permission, yet has merged:

repo PRs
ci-workflows #17, #18 (docker/login-action)
bankimporter #47, #51 (docker/login-action)
ecm #33 (astral-sh/setup-uv)

All are github-actions bumps that modify .github/workflows/.

Why it matters

The claim propagated into the README and into the PR bodies of the auto-merge
rollout, and it blocked an automated change to ak-visual-regression-tests:
the agent checked the App's actual permissions, found no workflows, read this
comment saying it was required, and correctly refused to proceed.

It would also have caused an unnecessary permission grant — workflows: write
lets a token rewrite CI definitions across every installed repo, which is not a
permission to hand out on a false premise.

Change

Documentation only. No behaviour change, so no version bump is required — the
floating v14 can pick this up on the next release.

🤖 Generated with Claude Code

v14.1.0 asserted that a GitHub App merging Dependabot's `github-actions`
PRs needs Workflows (read/write), "not optional", because those PRs edit
files under .github/workflows/. That is wrong.

The workflows permission governs pushing workflow files through the
Contents API. It does not gate merging a pull request that happens to
change them. Verified against this org: app/github-actions is itself an
App token and holds no workflows permission, yet has merged
github-actions bumps in ci-workflows (#17, #18), bankimporter (#47, #51)
and ecm (#33).

The claim had already done damage: it propagated into the README and
into the PR bodies for the auto-merge rollout, and it blocked an
automated change to ak-visual-regression-tests, which correctly refused
to proceed against documentation stating a required permission was
absent.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@lucas-d-ramos
lucas-d-ramos merged commit eb0938e into main Aug 21, 2026
2 checks passed
@lucas-d-ramos
lucas-d-ramos deleted the docs/correct-workflows-permission-claim branch August 21, 2026 11:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant