Install ProBot #5082
Install ProBot #5082
Conversation
This bot will help us to close issues after requesting more information to the user that reported it.
This bot will help us to clean up our repository and stay with issues that are actionable and we do want to work on them at some point. So, after some inactivity the bot will post a comment and if nobody responds to it, the issue will be closed.
What about the bug label?
We can already filter by emojis in github
Mergeable and dep looks good, but not sure if they are really helpful, we can just leave a comment.
We need to relabel some issues, I'll do that now. |
| autoAssign: false | ||
| blobLines: 7 | ||
| caseSensitive: true | ||
| keyword: "TODO" |
There was a problem hiding this comment.
we also have fixme and xxx in our code, some are in lowercase.
There was a problem hiding this comment.
This will work only for new code, anyway. The bot does not accept multiple keywords as far as I know and TODO is the standard way.
.github/no-response.yml
Outdated
| to our request for more information from the original author. With only the | ||
| information that is currently in the issue, we don't have enough information | ||
| to take action. Please reach out if you have or find the answers we need so | ||
| that we can investigate further. Thanks! |
There was a problem hiding this comment.
Maybe we could add a link to our docs here, I use this response for these cases
Closing this as the user hasn't responded or given more information, feel free to reopen with more information if you are still having this problem :).
| # https://probot.github.io/apps/stale/ | ||
|
|
||
| # Number of days of inactivity before an issue becomes stale | ||
| daysUntilStale: 45 |
There was a problem hiding this comment.
I think we could extend this number a little more, maybe two months?
There was a problem hiding this comment.
Hrm, my idea with this bot is not "just close the issues" but also "alert us that we are not paying attention to them". If we find that 45 is to early and distracting, we can increase this number later.
Anyway, if they are correctly labeled (Accepted, Desing decision, etc) it won't affect/distract us at all, though.
I don't want to put |
Wow! I didn't know that. I think that having a tag will make these issues more globally visible, though. |
Mergeable needs more research since I didn't take a deep look, but dep looks useful to me: we can immediately know if a PR depends on another one without reading the whole thread of comments and it's for free :) |
I'm -1 on another label here, i won't use this and already use the filtering in github. Also, our repo doesn't get a lot of reactions on issues either way. |
This PR adds config files for Stale and No Response and todo
Stale
This bot will
Status: staleAfter 7 days the issue was tagged as
Status: staleif there was no activity, it will be closed.No Response
This bot will
Needed: more informationtodo
This bot will create an issue every time that we push a
# TODO:in our code with the message and the lines affected.Delete Merged Branch
https://probot.github.io/apps/delete-merged-branch/
This bot will just delete branches that are merged automatically.
Reminders
https://probot.github.io/apps/reminders/
This bot will help us with issues for our Abandoned Project Policy
There are more bots that could help us to manage our repositories.
I think we can grow from here after we see how it works and how our flow is affected. At the moment I only request these bots to be installed in
rtfd/readthedocs.orgbut I'd like if we can configure them in all of our repos, though.Closes #4111