Triggering extended tests through PR comment #15101
Draft
+148
−1
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
github-actions
bot
added
the
development-process
|
Looks like it ran checks on the forked branch, I think that is what we want
|
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.
Which issue does this PR close?
Closes #14319
Rationale for this change
Allows to run extended tests on some PRs if needed, while skipping them by default on other PRs. The user experience of running the extended test suite should be roughly the same (check is shown in the PR actions tab, comment is marked with 🚀 emoji when the tests are triggered for the PR)
What changes are included in this PR?
Adding a new trigger event for extended tests -
workflow_dispatch, and a separate action which is checking all PR comments and issuing this dispatch event for the PR branch when theRun extended testscomment is detected.Are these changes tested?
Only manual tests on the fork (see here), unfortunately I am not aware of any better tests for Github actions.