10000 Disable miss-islington comments in check_run as well by ambv · Pull Request #583 · python/miss-islington · GitHub
[go: up one dir, main page]

Skip to content

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

Merged
merged 4 commits into from
Oct 4, 2022

Conversation

ambv
Copy link
Contributor
@ambv ambv commented Oct 4, 2022

Addresses #577

@codecov
Copy link
codecov bot commented Oct 4, 2022

Codecov Report

Merging #583 (cce2f8f) into main (2e6fc49) will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff            @@
##              main      #583   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           10        10           
  Lines         1017      1010    -7     
  Branches        67        66    -1     
=========================================
- Hits          1017      1010    -7     
Impacted Files Coverage Δ
tests/test_check_run.py 100.00% <ø> (ø)
miss_islington/check_run.py 100.00% <100.00%> (ø)
miss_islington/status_change.py 100.00% <100.00%> (ø)

@ewdurbin ewdurbin temporarily deployed to miss-islingt-disable-co-dvylnj October 4, 2022 22:22 Inactive
@ambv ambv requested review from ezio-melotti and Mariatta October 4, 2022 22:24
@ewdurbin ewdurbin temporarily deployed to miss-islingt-disable-co-dvylnj October 4, 2022 22:28 Inactive
# original_pr_number = title_match.group("pr")
# participants = await util.get_gh_participants(
# gh, original_pr_number
# )
Copy link
Member

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)

Copy link
Contributor Author

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.

@ambv ambv merged commit be7cbdd into main Oct 4, 2022
@ambv ambv deleted the disable-comments-in-check-run branch October 4, 2022 23:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0