Repository navigation
The publish step wrote the site one level too deep - #12
Merged
Merged
Conversation
The built site went to gh-pages at docs/<version>/, but this repository is already served at /docs/ — so it landed at /docs/docs/<version>/ while /docs/latest/ went on serving the MkDocs build mike had left there. Both URLs answered 200, which is why the green deploy said nothing. The publish step now calls go-fleettools/fleettools/cmd/pagespublish at a pinned tag: the version replaces <gh-pages>/<version>/ at the ROOT and nothing else, then versions.json in mike's format (what the Hextra fork's version selector reads), the latest link and the root redirect. It also removes the misplaced docs/ directory once, and only when that directory holds nothing but version directories. One block replaced verbatim, by a tool that refuses a file which does not hold it exactly; the pages are untouched. Co-Authored-By: Claude Opus 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 built site went to
gh-pagesatdocs/<version>/, but this repository is already served at/docs/— so it landed at/docs/docs/<version>/while/docs/latest/went on serving the MkDocs buildmikehad left there.Both answered 200, which is why the green deploy said nothing. Found by fetching the page after the migration merged.
The publish step now calls
pagespublishat a pinned tag: the version replaces<gh-pages>/<version>/at the root and nothing else, thenversions.jsonin mike's format — what the Hextra fork's version selector reads — thelatestlink and the root redirect. It also removes the misplaceddocs/directory once, and only when that directory holds nothing but version directories.One block replaced verbatim, by a tool that refuses any file which does not hold it exactly; the pages are untouched.
🤖 Generated with Claude Code