ci(template): Ignore build for doc changes#440
Closed
NickLarsenNZ wants to merge 1 commit intomainfrom
Closed
Conversation
Member
Author
|
Apparently this will break the required checks. So we would then need an initial job to see if there are any changes outside of docs, and then continue. Probably needs |
Member
Author
|
Closing as this has been done in recent operator workflow improvements |
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.
It makes little sense to build everything if only docs have changed.
Caution
Need to check if the "Stackable Build Pipeline" is a required check in Github Repo Settings. Would a PR with the build job skipped be allowed to merge?
I'd be happy to merge/roll out this change, and test it with a doc-only change.