Repository navigation
Publish manual: accept a fine-grained token as well as a deploy key - #104
Merged
Merged
Conversation
The Docs repository checkout takes secrets.DOCS_PUBLISH_TOKEN (falling back to the default token, which cannot push) next to the deploy key, so the one-time setup can be done entirely on the GitHub website. The README and the release page describe both routes. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QcYr11a5B65kS64MagbgF1
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
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.
Follow-up to #103: the "Publish manual" workflow can now use a fine-grained personal access token instead of a deploy key, so the one-time setup needs only the GitHub website (no
ssh-keygen).actions/checkoutof the Docs repository takestoken: ${{ secrets.DOCS_PUBLISH_TOKEN || github.token }}next tossh-key: ${{ secrets.DOCS_DEPLOY_KEY }}. A deploy key wins when both exist; with neither, the checkout still reads the public repository and the push fails with403as in the first run.documentation-site/README.mdand the manual's release page describe both routes.Validated: YAML parses; privacy, export, mkdocs strict and site validation pass locally. The workflow itself only runs on
main, so its first real run with a token is the manual run after this merges.Generated by Claude Code