ci: grant deploy workflow contents write permission#170
Merged
Conversation
The default GITHUB_TOKEN is read-only, so the gh-pages push in the deploy step fails with 403. format-bib.yml already declares this permission; deploy.yml was missing it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
The "Build and Deploy" workflow has been failing on master since June: the gh-pages push gets a 403 because the default
GITHUB_TOKENis read-only anddeploy.ymlnever requests write access.format-bib.ymlalready declarespermissions: contents: write— this adds the same block to the deploy job.Failing run for reference: https://github.com/sign-language-processing/sign-language-processing.github.io/actions/runs/28778740735
🤖 Generated with Claude Code