-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Add action to label mergeable PRs #9931
Conversation
This looks great to me, lmk when this is "ready for |
ddfec0f
to
f87c1a0
Compare
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.
[DO NOT MERGE] approving to trigger the workflow
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.
clicked wrong button
Reverting back to draft since I'm not sure this is workable since when GitHub reports a status (i.e. when Jenkins is done) I don't see any way to get the original pull request when the PR comes from a forked repo, so the main use case (approval happens, then Jenkins completes hours later) doesn't work. |
8289e4f
to
ea2665a
Compare
ba0a195
to
b9886e7
Compare
It has been a while since this PR was updated, @areusch please leave a review or address the outstanding comments |
1 similar comment
It has been a while since this PR was updated, @areusch please leave a review or address the outstanding comments |
closing this to keep it from languishing anymore, an RFC will be coming soon that should address the underlying issue of merging PRs |
Developers often have to ping a committer once their PRs are both passing in CI and are approved. This helps facilitate this process by marking such PRs with a label
ready-for-merge
so committers can easily filter for outstanding PRs that need attention.Tested in driazati#2 via https://github.com/driazati/tvm/actions/workflows/ready_for_merge.yml