Skip to content

ci: let the cascade workflow enable auto-merge on its PR - #242

Merged
lisachenko merged 1 commit into
4.xfrom
fix/cascade-auto-merge-permission
Oct 6, 2026
Merged

lisachenko merged 1 commit into
4.xfrom
fix/cascade-auto-merge-permission

Conversation

@lisachenko

Copy link
Copy Markdown
Member

What and why

The "Cascade 4.x into master" workflow fails in "Open/refresh cascade PR" with:

Enabling auto-merge on PR #240
GraphQL: Resource not accessible by integration (enablePullRequestAutoMerge)

The August 25 run failed the same way. Without a CASCADE_TOKEN secret, the step runs with GITHUB_TOKEN under permissions: contents: read. Enabling auto-merge also needs contents: write, so this PR grants it.

After merging

  • The push to 4.x re-runs the workflow, which should then enable auto-merge on the cascade PR.
  • If it still fails with the same message, the repository's Actions settings probably cap the GITHUB_TOKEN at read-only ("Workflow permissions"). In that case the CASCADE_TOKEN PAT, which the workflow already supports, is the remaining fix.
  • Auto-merge also requires "Allow auto-merge" to be enabled in the repository settings.
  • The merge conflict of Cascade merge: 4.x into master #240 is resolved separately by the master PR chore: merge 4.x into master.

🤖 Generated with Claude Code

https://claude.ai/code/session_019bYFRwMWKndKaj6SemwDn2


Generated by Claude Code

"Open/refresh cascade PR" fails with "Resource not accessible by
integration (enablePullRequestAutoMerge)": without a CASCADE_TOKEN the
job runs with GITHUB_TOKEN, and enabling auto-merge needs contents: write
next to pull-requests: write.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019bYFRwMWKndKaj6SemwDn2
@lisachenko
lisachenko marked this pull request as ready for review October 6, 2026 20:59
@lisachenko
lisachenko merged commit 1f096af into 4.x Oct 6, 2026
7 checks passed
@lisachenko
lisachenko deleted the fix/cascade-auto-merge-permission branch October 6, 2026 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants