Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Configure MLflow repository with Probot-stale #1841
What changes are proposed in this pull request?
As discussed, we want to be able to deal with older issues in a better way! Probot will go through issues and mark ones that have not been interacted with for a configured amount of time as stale. Some configurable number of days after an issue marked as stale has not been engaged with, Probot will close that issue due to a lack of activity.
In this PR, I propose marking an issue as stale if it has not been interacted with for 3 weeks. The issue would then be closed if it has not been engaged with for 2 months after it has been marked as stale. We can make this more aggressive as we develop more processes around dealing with issues! Notably, issues marked as enhancement are ignored by Probot, since it's likely that those would have longer lifespans.
As discussed, this would increase the visibility of issues and encourage more progress on them. This, combined with eventual JIRA integration, should dramatically raise the visibility of issues.
How is this patch tested?
Test in prod!
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s) does this PR affect?
How should the PR be classified in the release notes? Choose one:
Got some feedback from @mateiz that there may be issues that we want to fix, where users may not need to engage, and it might take us longer than the stalebot SLA to fix. In this case, we still want to have the issue left open. To this end, I've created a will-fix label and exempted it from staleness checks