Don't re-run tests on push
#5727
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
The tests don't need to run again on `push` after they've already run on the PR and in the merge queue.
This action is no longer functional. A new automation for this can be re-added later if needed.
obycode
requested review from
BowTiedDevOps,
wileyj and
kantai
and removed request for
a team
jferrant
approved these changes
Jan 17, 2025
kantai
approved these changes
Jan 17, 2025
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The tests are currently set to run on PRs, in the merge queue, and again on push to
develop,master, ornext. This removes the duplicate run on push.The second commit also removes the
docs-praction, because it no longer works, and making the changes to the docs repo need adjustments to the automation before it could be re-enabled.