Skip to content

fix(ci): add write permissions to update-flake-lock workflow#2642

Closed
DreadPirateRobertz wants to merge 1 commit intosteveyegge:mainfrom
DreadPirateRobertz:fix/flake-lock-permissions-2630
Closed

fix(ci): add write permissions to update-flake-lock workflow#2642
DreadPirateRobertz wants to merge 1 commit intosteveyegge:mainfrom
DreadPirateRobertz:fix/flake-lock-permissions-2630

Conversation

@DreadPirateRobertz
Copy link
Contributor

The update-flake-lock workflow needs contents:write (push branch) and pull-requests:write (create PR). Without these, the default GITHUB_TOKEN causes 403 errors. Fixes #2630

…gge#2630)

The workflow needs contents:write to push the flake.lock update branch
and pull-requests:write to create the PR. Without these, the default
GITHUB_TOKEN causes a 403 error.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Executed-By: gastown/crew/zhora
Rig: gastown
Role: crew
steveyegge added a commit that referenced this pull request Mar 17, 2026
The workflow needs contents:write (push branch) and pull-requests:write
(create PR) for peter-evans/create-pull-request to function.

Fixes #2630

Co-Authored-By: DreadPirateRobertz <DreadPirateRobertz@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@steveyegge
Copy link
Owner

Fix-merged to main in ae28719. Thank you @DreadPirateRobertz!

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.

fix(ci): update-flake-lock workflow fails with 403 — missing GITHUB_TOKEN permissions

2 participants