Conversation
When a commit is pushed or merged into one of the release branches (master, maint/*) then push the documentation update to gh-pages.
Member
Author
|
Indeed, the goal here is that pull request builds do not get a documentation update: |
Member
Author
|
I tested this pretty extensively on my fork. Unless I did something like screw up the configuration of the PAT variables for this repo (entirely possible), this should be 👌. Going to merge so that we can get a doc update for the latest release on the website. |
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.
When a commit is pushed or merged into one of the release branches (
master,maint/*) then push the documentation update to gh-pages.