-
Notifications
You must be signed in to change notification settings - Fork 69
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
Automatically assign collaborators to new issues #28
Comments
@kevinmehall do you have a link to this? |
https://github.com/nrc/highfive is the code, https://github.com/rust-highfive?tab=activity is Rust's instance of it. |
@johnnyman727 do you still think this is a good idea? I don't. |
@Frijol I think it's a good way to make sure issues get labeled properly. If it's urgent the collaborator can hand it off to whomever can handle it best. If not, they can just label it and un-assign themselves. Why do you think it's not a good idea? |
If an issue is assigned to someone, I won't click on it and work on it, because I assume the assigned person is doing it. Better to have open issues that people can pick up and start working on. It also fallaciously assumes that every issue is worth working on right away. |
Yes, the assigned collaborator should be responsible for assigning/un-assigning people and marking the urgency with a label. In any case, there are more urgent priorities than this at the moment :) |
@tcr do you think this is closed as of us having @tessel-highfive ? |
We need to automatically assign collaborators to issues on Tessel repos. Apparently the rust-lang group has open sourced the code they use to do that.
The text was updated successfully, but these errors were encountered: