Update CLAUDE.md deploy docs to the PR-based flow#8
Merged
Conversation
main is branch-protected and rejects direct pushes, so document the required flow: push a branch, open a PR, wait for the "Test deployment" check, then merge (merging triggers the GitHub Pages deploy). Remove the stale master/unrelated-history commit-tree workaround; local main now tracks origin/main cleanly. Co-Authored-By: Claude Opus 4.8 <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.
Follow-up to #7. That PR revealed the CLAUDE.md deploy instructions were stale:
mainis branch-protected and rejects directgit push origin main, but the doc described pushing straight tomain(and amaster/unrelated-historycommit-treeworkaround that no longer applies).Updates the Deploying section to the real flow: push a branch, open a PR, wait for the required "Test deployment" check, then merge (merging triggers the GitHub Pages deploy). Also notes to stage only your change and leave unrelated working-tree edits unstaged.
Docs only.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com