-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Allow everyone to assign labels with rustbot #4595
Conversation
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.
Looks good to me
@bors r+ |
📌 Commit 79c4543 has been approved by |
Allow everyone to assign labels with rustbot Also allows people to claim issues even if they aren't part of the org changelog: none
💔 Test failed - status-appveyor |
Looks like some loop lint broke? |
@bors retry ? |
@lzutao: 🔑 Insufficient privileges: not in try users |
@bors retry |
Allow everyone to assign labels with rustbot Also allows people to claim issues even if they aren't part of the org changelog: none
💔 Test failed - status-appveyor |
@bors retry may have been spurious (error: no such subcommand: |
Allow everyone to assign labels with rustbot Also allows people to claim issues even if they aren't part of the org changelog: none
💔 Test failed - status-appveyor |
@bors retry |
hey @bors are you still there? |
@bors retry (or do I have to r=flip1995?) |
@bors r=flip1995 |
💡 This pull request was already approved, no need to approve it again.
|
📌 Commit 79c4543 has been approved by |
It has to wait on #4628 Looking at https://buildbot2.rust-lang.org/homu/queue/clippy bors is stuck on #4627 |
Oh thanks, I was just expecting the |
Allow everyone to assign labels with rustbot Also allows people to claim issues even if they aren't part of the org changelog: none
☀️ Test successful - checks-travis, status-appveyor |
Also allows people to claim issues even if they aren't part of the org
changelog: none