Re: GitGitGadget on git/git, was Re: Should we auto-close PRs on git/git?
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Nov 22, 2019, 14:43 UTC
- Message-ID
- <nycvar.QRO.7.76.6.1911221542511.31080@tvgsbejvaqbjf.bet>
- In-Reply-To
- <nycvar.QRO.7.76.6.1911221430510.31080@tvgsbejvaqbjf.bet>
Hi Peff,
On Fri, 22 Nov 2019, Johannes Schindelin wrote:
Show 23 quoted lines
> On Thu, 21 Nov 2019, Jeff King wrote: > > > On Mon, Nov 18, 2019 at 07:37:57PM +0100, Johannes Schindelin wrote: > > > > > To build some confidence in my patches (as you probably know, I do > > > not trust reviews as much as I trust real-life testing, although I > > > do prefer to have both) I "kind of" activated it on my fork, limited > > > to act only on comments _I_ made on PRs (and sending only to me > > > instead of the list), and it seems to work all right, so far. I > > > cannot say for sure whether it handles the PR labels correctly, but > > > I guess time will tell, and I will fix bugs as quickly as I can. > > > > Yeah, that makes sense to me. Going from one repo to three is not much > > worse than going to two, so it's good to have a testing area, too. > > > > Do you want any third-party testing there (e.g., a user who isn't you > > making a PR against dscho/git)? > > While that would be nice, my fork is a mess and not really set up to > provide any useful target branch... > > The real proof of the concept will come when the first git/git PR will > be submitted.
Seems to have worked: https://public-inbox.org/git/pull.670.git.git.1574433665.gitgitgadget@gmail.com/
Ciao, Dscho