Skip to content

Commit 9ee40bf

Browse files
mschmickingclaude
andcommitted
docs: record the setting release-please needs to open a PR
It is off by default: Settings -> Actions -> General -> Workflow permissions -> 'Allow GitHub Actions to create and approve pull requests'. Without it the workflow does everything right — reads the manifest, computes 0.1.0 -> 0.1.1, creates the branch — and then fails on the final API call. The symptom is a stale release-please--branches--main--* branch and a red check with no obvious cause in the config. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 parent cab77a4 commit 9ee40bf

1 file changed

Lines changed: 8 additions & 0 deletions

File tree

docs/GOING-PUBLIC.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,14 @@ These change how merges behave, and the release automation depends on them.
2424
- [ ] **Settings → General → Pull Requests** → enable **Automatically delete head
2525
branches**
2626

27+
- [ ] **Settings → Actions → General → Workflow permissions** → tick **Allow GitHub
28+
Actions to create and approve pull requests**
29+
30+
> **release-please cannot work without this.** It is off by default. The workflow
31+
> otherwise runs, computes the next version, creates its branch, and then fails at the
32+
> final step with "GitHub Actions is not permitted to create or approve pull requests".
33+
> A stale `release-please--branches--main--...` branch is the symptom.
34+
2735
- [ ] **Settings → Rules → Rulesets** (or Branches → branch protection) for `main`:
2836
- [ ] Require a pull request before merging
2937
- [ ] Require status checks to pass, and select:

0 commit comments

Comments
 (0)