-
-
Notifications
You must be signed in to change notification settings - Fork 39
Disable miss-islington comments in check_run as well #583
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## main #583 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 10 10
Lines 1017 1010 -7
Branches 67 66 -1
=========================================
- Hits 1017 1010 -7
|
# original_pr_number = title_match.group("pr") | ||
# participants = await util.get_gh_participants( | ||
# gh, original_pr_number | ||
# ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you elaborate a bit more on the logic here?
When is is_automerge
true? When the automerge
label is applied to the issue or when the backport PR was approved by a core-dev review? Or both?
And what's the difference between the participants of pr_number
and original_pr_number
?
IIUC now in case of failure you are pinging the participants of the backport pr -- does that (only?) include whoever merged the backport PR?
(cc @DanielNoord)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I commented out this code because it's no longer covered by tests, i.e. now really only auto-merges should emit comments on PRs.
Addresses #577