Skip to content

Conversation

@miss-islington
Copy link
Contributor

@miss-islingtonmiss-islington commented May 10, 2022

(cherry picked from commit f1bbcba)

Co-authored-by: CAM Gerlach CAM.Gerlach@Gerlach.CAM

Automerge-Triggered-By: GH:serhiy-storchaka

…rsions & features (pythonGH-92529) (cherry picked from commit f1bbcba) Co-authored-by: CAM Gerlach <CAM.Gerlach@Gerlach.CAM>
@miss-islingtonmiss-islington requested a review from a team as a code ownerMay 10, 2022 06:30
@miss-islington
Copy link
ContributorAuthor

@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
ContributorAuthor

@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
ContributorAuthor

@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
ContributorAuthor

@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
ContributorAuthor

@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
ContributorAuthor

@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ .

@CAM-Gerlach
Copy link
Member

Is there a reason @miss-islington has to spam the backport, and our notifications, with a stream of identical comments just stating the status check was a success over and over? Can it only comment once if the status check failed, and edit its comment if that changes, like other bots do?

@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason: Base branch was modified. Review and try the merge again..

@miss-islington
Copy link
ContributorAuthor

@miss-islington: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
ContributorAuthor

@miss-islington: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason: 3 of 6 required status checks are expected..

@miss-islington
Copy link
ContributorAuthor

@miss-islington: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
ContributorAuthor

@miss-islington: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason: 3 of 6 required status checks are expected..

2 similar comments
@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason: 3 of 6 required status checks are expected..

@miss-islington
Copy link
ContributorAuthor

Sorry, I can't merge this PR. Reason: 3 of 6 required status checks are expected..

@miss-islington
Copy link
ContributorAuthor

@miss-islington: Status check is done, and it's a success ✅ .

@miss-islingtonmiss-islington merged commit 635b62a into python:3.11May 10, 2022
@miss-islingtonmiss-islington deleted the backport-f1bbcba-3.11 branch May 10, 2022 09:55
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@miss-islington@CAM-Gerlach@serhiy-storchaka@bedevere-bot