GH-419: Follow-up fix to support unstable builders triggering #436
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
pythonGH-434 attempted to support triggering unstable builder with comment-based triggering It had two flaws that are fixed in this follow-up PR: 1. Needed to unpack the `event` property 2. If we are left with no builders after filtering, need to avoid the super() call (otherwise we end up triggering ALL builders O_O)
|
Well, I trust you, let's see how it goes :-) |
This was referenced Nov 1, 2023
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.
GH-434 attempted to support triggering unstable builder with comment-based triggering It had two flaws that are fixed in this follow-up PR:
eventproperty