-
Notifications
You must be signed in to change notification settings - Fork 76
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
Support @rustbot move $repo
#166
Comments
What is the use case of this command ? |
This would be nice to have, people often open issues on rust-lang/rust that should be transferred to somewhere else. Even though I have perms for that repo, I don't have perms for, say, clippy, so I can't move anything to clippy. I think it would be fine if this command was entirely unrestricted, but it should at least be so that all org members can do it. |
How often, more or less? (Asking because I am not usually on the first line for new issues). IIUC the GH documentation, users granted the Personally I find this a potential source of abuse and disruption. Maybe I'm just a bit pessimistic 🙂 |
I don't have numbers. Not that often, but every once in a while, clippy being the most common.
Both! So this would already be useful if it was restricted to org members. |
I fairly often transfer issues, but I tend to have write permissions where needed. I do think it would be very useful, and I think limiting to org members would be best to start with. I'm not clear, though. Is this issue about transferring issues, or repositories? The first link above is about transferring a repository (which I don't think we need). |
Yeah, transfering issues. |
bikeshed: maybe it should be would rustbot then mark the comment as hidden/complete after the move? |
My bikeshed would be "transfer" to use the same lingo as GitHub. (I still assert this issue seems to originally have been to move a repo.) |
Does GitHub support this?
https://discordapp.com/channels/442252698964721669/443148290352218115/624290071985782784
The text was updated successfully, but these errors were encountered: