ci: don't run long tests on docs-only PRs #4562
Merged
Conversation
This file contains 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
I want to keep the docs up to date, and sometimes that requires fussy management of version numbers, particularly as we invest in multi-branch workflows to support point releases (e.g. #4545). If *only* the docs changed, skip the long-running rust tests, because we don't need to validate rust functionality on docs changes.
conorsch
force-pushed
the
ci-no-rust-tests-on-docs-changes
branch
from
76ec232 to
2a739ab
Compare
cratelyn
approved these changes
Jun 5, 2024
1 task
1 task
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.
Describe your changes
I want to keep the docs up to date, and sometimes that requires fussy management of version numbers, particularly as we invest in multi-branch workflows to support point releases (e.g. #4545). If only the docs changed, skip the long-running rust tests, because we don't need to validate rust functionality on docs changes.
Issue ticket number and link
Checklist before requesting a review
If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason: