Do not report back to GitHub with the PR buildeers #193
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
It seems that the PR builders can get confused if a pull requests contains commits of another pull request when ussing the `test-with-buildbots` label. For instance, this PR: python/cpython#20006 included messages that report to a commit that lives in another PR where the label was added. To avoid this, exclude the PR builders from the GitHub notification system.
|
What is the status of this PR? |
|
It should be merged |
|
Thanks. Better late than never. |
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.
It seems that the PR builders can get confused if a pull requests
contains commits of another pull request when ussing the
test-with-buildbotslabel. For instance, this PR:python/cpython#20006
included messages that report to a commit that lives in another PR where
the label was added. To avoid this, exclude the PR builders from the
GitHub notification system.