[Workflows] add a workflow that can be manually triggered on a PR. #7942
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
BenjaminBossan
approved these changes
May 14, 2024
| required: true | ||
| test_command: | ||
| description: 'Test command to run (e.g.: `pytest tests/pipelines/dit/`). Any valid pytest command can be provided.' | ||
| required: true |
There was a problem hiding this comment.
Would it make sense to have a default here?
There was a problem hiding this comment.
I think not because having a default here wouldn't really help the case IMO.
yiyixuxu
approved these changes
May 14, 2024
sayakpaul
added a commit
that referenced
this pull request
Dec 23, 2024
…7942) * add a workflow that can be manually triggered on a PR. * remove sudo * add command * small fixes.
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.
What does this PR do?
Currently, we manually run the SLOW tests for PRs where applicable to ensure the changed components are robust enough to merge. This is burdensome.
How about a workflow that we can trigger with a few clicks and run the desired tests within our CI runner?
This PR adds such a workflow.