Re: Should we auto-close PRs on git/git?

From: Jeff King <peff@peff.net>
Date: Nov 14, 2019, 07:41 UTC
Message-ID: <20191114074117.GB17186@sigill.intra.peff.net>
In-Reply-To: <nycvar.QRO.7.76.6.1911131234380.46@tvgsbejvaqbjf.bet>

On Wed, Nov 13, 2019 at 01:04:35PM +0100, Johannes Schindelin wrote:

Show 12 quoted lines

> > We talked a while ago about having GitGitGadget operate on git/git,
> > rather than on a separate mirror. That would automatically help at least
> > one class of PR-opener: people who want their patches to reach the list
> > but didn't realize they should be using gitgitgadget/git.
> >
> > I don't remember what the technical blockers are for getting that set
> > up, but it seems like a strictly nicer outcome than auto-closing their
> > PR.
> 
> Okay, here are a couple of technical challenges, off the top of my head:
> [...]
> Not an easy, nor a small project, I am afraid.

Yow. That's a lot more involved than I was hoping for.

Thanks for writing it up. Some of the points raised were interesting. I do think we'd want git/git (the repository) to remain read-only if possible. If GitHub's permissions model is a limiting factor here, let me know and I can try to bring it to the attention of the right people.

-Peff