Repository navigation
ci: publish docs only when master changes - #131
Merged
Merged
Conversation
Move the GitHub Pages deploy from develop to master: push to master builds and deploys, while pull requests into develop or master only build to catch errors. This ties the published docs to the release (master) branch. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 07742674-f983-4ae2-a4d1-36972dad3598
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.
Changes the Docs workflow so GitHub Pages is published only when the
masterbranch changes, instead ofdevelop.pushtrigger:develop→master(builds and deploys).pull_requesttrigger:develop→develop,master(build-only validation, no deploy).github.ref == 'refs/heads/master'(wasdevelop).workflow_dispatchstill allowed (deploys only when run onmaster).This ties the published documentation to the release (
master) branch while keeping doc-build validation on PRs.Note: publishing will only occur once
masterreceives these docs changes (e.g., on the nextdevelop→masterrelease merge).