Add explicit types to pull_request trigger
#426
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
Includes the defaults as well as the 'edited' and `ready_for_review` types.
TimothyWillard
requested review from
pearsonca,
jcblemai,
fang19911030 and
emprzy
TimothyWillard
added
bug
jcblemai
approved these changes
Dec 12, 2024
pearsonca
approved these changes
Dec 12, 2024
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.
This pull request modifies the pull request related triggers slightly (see below). This is being merged into
maininstead ofdevbecause we want to maintain a consistent set of actions across branches (workflow is determined by base branch) and will pull these edits frommainback intodevafter merging.Does this pull request make any user interface changes? If so please describe.
The user interface changes are the CI GitHub actions will now trigger when a PR is edited (most importantly for GH-412 when the target branch is changed) and when a PR is changed from draft to ready for review. The previous pull request triggers for actions still hold as well.
What does your pull request address? Tag relevant issues.
This pull request addresses GH-412.