A stale PR has not activity for some length of time. https://github.com/probot/stale
The policy file example shown on that link it pretty easy to follow, so I'll avoid pasting a wall of text into this email. This seems like a pretty valuable and much-needed piece of management-y software. Unfortunately, I was informed Apache Infra could not grant write perms to this GitHub plugin. I'd like to understand how we decide which plugins on GitHub get whitelisted? -s On Wed, Sep 12, 2018 at 7:39 AM Dave Fisher <dave2w...@comcast.net> wrote: > Hi - > > What if the stale PR is from a new community member who is trying to make > a contribution? Those should be handled by a committer with direct > discussion. > > Regards, > Dave > > Sent from my iPhone > > > On Sep 11, 2018, at 7:40 PM, Hagay Lupesko <lupe...@gmail.com> wrote: > > > > Im also interested in this PR policy automation. > > > > For Apache MXNet, there is no automation that I am aware of that handles > > that. And it can be super helpful in handling stale PRs... > > > > Hagay > > > >> On Tue, Sep 11, 2018, 12:07 Sid Anand <san...@apache.org> wrote: > >> > >> Hi Folks! > >> I wanted a policy-driven approach to automatically label, comment, and > >> close inactive/stale PRs. Probot does this, but need some write perms to > >> GitHub. > >> > >> https://github.com/probot/stale > >> > >> I just learned this is not possible per > >> https://issues.apache.org/jira/browse/INFRA-17005 > >> > >> How are other projects solving this problem? And why is probot not on > say > >> an approved list of GitHub integrations? > >> > >> -s > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
