Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Miss-islington should not self-assign PR that failed to backport #154

Open
Mariatta opened this issue Sep 14, 2018 · 1 comment
Open

Miss-islington should not self-assign PR that failed to backport #154

Mariatta opened this issue Sep 14, 2018 · 1 comment

Comments

@Mariatta
Copy link
Member

It should assign it back to the approver.
@Mariatta
Copy link
Member Author

GitMate.io thinks possibly related issues are #7 (Trigger the backport by leaving comments to miss-islington), python/core-workflow#243 (Assign the failed PR to be backported to the core dev who merged it), #88 (Assign the failed PR to be backported to the core dev who merged it), #26 (Notify when backport PRs failed), and #94 (Approved backport PR was not automerged).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Mariatta