We have script to help reviewers checkout PR’s in git, either in their own repo or just doing it in ~/tmp or something into a new repo.
So, I would run: > checkout-pr 999 in the tmp directory, and end up with a local version that I can then build and do whatever with. would that help? On March 14, 2018 at 10:08:47, Gilles (gil...@harfang.homelinux.org) wrote: On Tue, 13 Mar 2018 11:43:17 -0400, ajs6f wrote: >> On Mar 13, 2018, at 11:20 AM, Gilles <gil...@harfang.homelinux.org> >> wrote: >> >> >> I didn't find it very easy to cooperate with developers who fork on >> GitHub and submit PRs. I've now found the "git" command that creates a >> branch from a PR, but it would be so much more comfortable to just >> switch directory and do "git pull". >> > > Just as a point of information, it is possible to reverse the Github > <- Apache mirroring most projects use to be Github -> Apache. It seems that a good-enough-for-me solution would be to "clone" (on my local system) the repository forked by the GSoC participant. Does it make sense? Thanks, Gilles > What > that means is that merging PRs from Github becomes one click in the > Github UI. > > There are other consequences, of course, especially related to other > integrations Commons may be using (e.g. integration between Github > and > JIRA). > > Of course, INFRA are the folks to talk to if this sounds interesting. > At Apache Jena, we looked into it but have taken no action because we > still have some open questions about when some of our workflow > integrations will become possible with "reversed mirroring". > > Adam Soroka ; aj...@apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
