Build docs in own workflow #6991
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
radarhere
reviewed
Mar 4, 2023
Run valgrind tests when GitHub Actions file changes
radarhere
reviewed
Mar 5, 2023
Co-authored-by: Andrew Murray <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
So far the
make doccheckdocs test has been piggybacking on the maintest.ymlbuild.We have a pretty big (and slow!) CI matrix, I think it's time to split the it into its own workflow.
This way, we can run the docs workflow only when the docs change (or the docs workflow file), and have the other workflows ignore docs-only changes.
It will make it much quicker for docs-only PRs.
For example, the first commit here still ran all the workflows:
And the second only ran the docs (plus linting):