Docs: Document the docs/release publishing flow - #5729
Merged
Conversation
cloutiertyler
enabled auto-merge
August 12, 2026 18:27
JulienLavocat
approved these changes
Aug 12, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 12, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 12, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Aug 12, 2026
joshua-spacetime
removed this pull request from the merge queue due to the queue being cleared
Aug 12, 2026
bfops
enabled auto-merge
August 12, 2026 20:29
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.
Description of Changes
Adds a "Releasing the Docs" section to
docs/README.mddocumenting how the live docs site is published:docs/releasebranch (via the Docs / Publish workflow), not frommaster.docs/release:git push --force origin origin/master:docs/releasellms.mdoutput directly todocs/release, so that branch always drifts ahead ofmasterwith disposable build-output commits.docs/release.This removes the ambiguity where
docs/releasehad commits not onmasterand it was unclear how to update it without losing them.API and ABI breaking changes
None — documentation only.
Expected complexity level and risk
1
Testing