Repository navigation
fix: isolate documentation PRs by build target and preserve new sources - #56
Merged
Merged
Conversation
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 #55.
All documentation builds previously used the default
create-pull-request/patchbranch. A scheduled master build or a manual build for another release could replace changes in a pending documentation PR. Set the PR branch tocreate-pull-request/docs-${{ inputs.ref || 'master' }}so each build ref maintains its own PR. Scheduled runs and manual master builds sharedocs-master, while release builds use branches such asdocs-v6.0.1.Also fix timestamp cleanup aborting publication when a build introduces an untracked
_sources/index.rst.txtin an existing tracked directory. Restrict cleanup to tracked, modified documentation index sources and read null-delimited paths.Add five fixture-based regression tests and a dedicated CI workflow covering new sources, timestamp-only changes, substantive changes, release-only updates, and preservation of previous versions.
Validation:
bash -n scripts/update_docs.shandgit diff --checkpass.Full upstream Sphinx and end-to-end Actions execution were not run locally.