Repository navigation
Grant contents: write so the deploy workflow can publish the site - #205
Merged
Merged
Conversation
…ages The permissions block added in 5a8f948 only granted packages: write, which drops the GITHUB_TOKEN's contents scope. maven-scm-publish-plugin then fails to push the site to gh-pages with a 403. Co-Authored-By: Claude Opus 5.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.
Problem
The "Publish site" step of the Java CI with Maven and Deploy workflow fails on every push to master:
Commit 5a8f948 ("publish to GitHub Packages instead") added a top-level
permissions:block with onlypackages: write. When a workflow declarespermissions, every scope it leaves out is set tonone, so theGITHUB_TOKENlosescontents: write, andmaven-scm-publish-plugincan't push togh-pages. The snapshot publish to GitHub Packages in the same job still succeeds.The
gh-pagesbranch was last updated on 2023-03-02, so the published site is stale.Change
Add
contents: writenext topackages: writein.github/workflows/deploy.yml. Nothing else changes.Verification
The workflow only runs on pushes to master, so this PR can't exercise it. After merging, the "Publish site" step of that run should succeed, and
gh-pagesshould get a new "Site checkin for project hap-java" commit.🤖 Generated with Claude Code