I think we need to be able answer the question “Why are there so many inactive PRs?" before we automate their removal. If perfectly good changes are being ignored, we have a problem.
Removing branches of merged PRs and protecting the main branch make sense. > On 20 Feb 2021, at 18:30, Pavel Tupitsyn <ptupit...@apache.org> wrote: > > +1 > > - Close inactive PRs (1 month or so?) > - Enable main branch protection (no force pushes, require linear history, > require status checks) > > On Sat, Feb 20, 2021 at 2:31 PM Petr Ivanov <mr.wei...@gmail.com> wrote: > >> Hi, Igniters! >> >> >> When we started Ignite 3.x in new repository, not only we have received a >> chance to cleanup codebase, but to maintain some order in development >> tools, like GitHub. >> Currently in 2.x repository we have lots of stalled PRs and branches, >> which not only clog the repository, but also indirectly influence TC >> performance (due to necessity to check for updates every ref: branches and >> PRs). >> >> Could I suggest we devise some recommendations for using PR's and branches >> in new repo and add some rules about stalled PRs at least, like closing >> them if inactive for some time. >> Also we can activate some settings in repo's configuration, like auto >> delete branch after PR is merged. >> >> >> WDYT?
