The lingering pull requests are just backlog. I know that the asfgit user can automatically close PRs too, since it does in Spark. I remember it can't close PRs opened against branches other than master though, and neither can committers / administrators. In fact I don't think anyone except asfgit can close a PR someone else opened, and it will close things only on a merge.
I don't know the details of how this is set up -- are you already in contact with INFRA? But I know some degree of automation is available. On Fri, Jun 13, 2014 at 3:54 AM, Robert Metzger <[email protected]> wrote: > If you look at Apache Spark (which is using the GitHub integration for > quite some time now), it seems that they have exactly the situation you've > described: A lot of lingering pull requests: > https://github.com/apache/spark/pulls?direction=desc&page=8&sort=created&state=open > Github has support for specifying administrators for individual > repositories. If you want, I can ask INFRA if there is a way to solve the > problem. > > > On Fri, Jun 13, 2014 at 12:10 AM, Stephan Ewen <[email protected]> wrote: > >> Hi all! >> >> We are using pull requests against the github mirror. >> >> Once we merged the patch represented by the pull request, we cannot close >> the pull request, or change any status. We need to wait the user that >> opened the pull request to close it. >> >> This will probably lead to a lot of lingering pull requests and we need to >> manually cross check with jira to figure out whether pull requests are >> merged or not. >> >> It would be nice if committers had the permission to close pull requests >> against the github mirror repository. >> >> Has anyone experiences with that? >> >> Thanks, >> Stephan >>
