-
-
Notifications
You must be signed in to change notification settings - Fork 3.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
Add Probots #4111
Comments
@humitos originally brought this up internally, though we sidelined the work as we have a lot of bigger priorities on our roadmap. I think this is a good list to get started with. A few notes:
I think a few triage clarifications are needed:
|
Oh, also, I think automating branch deletion is another plugin that would be easy to configure and get started with: |
Good points, @agjohnson. I agree. I also don't know how I feel about Probot Stale, in general, but it was worth bringing up. I'm actually in favor of simply not including it as one of the one's we start with; I think that it's better to wait a bit. I think we should update the triaging guides or simply send around a re-read to triagers about the label differences. If we all used the same labels the same way, it would be better for the whole project. Thanks for your clarifications.
|
Anthony opened a PR regarding the guidelines upgrade at #4180 |
I want to start working on this because I think this could have been very useful and the effort that we need to set this up is probably smaller than the one we need to keep our issue tracker clean. I'm marking it as design decision because we may want to tweak more things or setup more aggressive bots still, but I will start with the simple ones/not invasive. |
Thanks, @humitos. Looking forward to seeing these. I think we should also add a note to the contributing docs about having bots and what they do, too, when we add them. |
Why
I want to add probots because I think that they can significantly make it easier for us to do triaging, and will relieve the maintainers of some pressure.
Wait, what are probots?
They're automated scripts that interact with GitHub issues and basically do some work for you, such as checking that users respond in times, that old threads are locked, and other things which are easy for a bot to do but laborious for maintainers.
Ok, which ones?
What do you think?
The text was updated successfully, but these errors were encountered: