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.

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

Closed
Centril opened this issue Sep 19, 2019 · 9 comments · Fixed by #1780
Closed

Support @rustbot move $repo #166

Centril opened this issue Sep 19, 2019 · 9 comments · Fixed by #1780
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@Centril
Copy link

Centril commented Sep 19, 2019

Does GitHub support this?

https://discordapp.com/channels/442252698964721669/443148290352218115/624290071985782784

@Centril Centril added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Sep 19, 2019
@Centril Centril removed the good first issue Good for newcomers label Sep 19, 2019
@kellda
Copy link
Contributor

kellda commented Nov 5, 2020

What is the use case of this command ?

@Noratrieb
Copy link
Member

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.

@apiraino
Copy link
Contributor

people often open issues on rust-lang/rust that should be transferred to somewhere else

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 Transfer issues permission should have Write, Maintain and Admin permissions on the repository (unclear if on the source repo, destination repo or both).

Personally I find this a potential source of abuse and disruption. Maybe I'm just a bit pessimistic 🙂

@Noratrieb
Copy link
Member

I don't have numbers. Not that often, but every once in a while, clippy being the most common.

unclear if on the source repo, destination repo or both).

Both!

So this would already be useful if it was restricted to org members.

@ehuss
Copy link
Contributor

ehuss commented Feb 13, 2024

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).

@Noratrieb
Copy link
Member

Yeah, transfering issues.

@fbstj
Copy link

fbstj commented Feb 14, 2024

bikeshed: maybe it should be move-to instead?

would rustbot then mark the comment as hidden/complete after the move?

@ehuss
Copy link
Contributor

ehuss commented Feb 14, 2024

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants