Re: Github usage

Thanks for all the suggestions. I see that there are things to try before bothering INFRA. ;-) Regards, Gilles On Thu, 15 Mar 2018 14:03:35 -0400, Otto Fowler wrote: https://github.com/apache/metron/tree/master/dev-utilities/committer-utils if you just want the bash On March 15, 2018 at

Re: Github usage

https://github.com/apache/metron/tree/master/dev-utilities/committer-utils if you just want the bash On March 15, 2018 at 13:51:00, ajs6f (aj...@apache.org) wrote: One gotcha that has bit me before-- if the PR isn't rebased over the current master (assuming you are merging into master) it may

Re: Github usage

One gotcha that has bit me before-- if the PR isn't rebased over the current master (assuming you are merging into master) it may still be merge-able because maybe there aren't any conflicts. (E.g. maybe no one has worked on that section of the codebase since the PR's branch was branched.) But

Re: Github usage

Oh, I was looking at the wrong version of Debian I think. On 15 March 2018 at 11:01, Gilles wrote: > On Thu, 15 Mar 2018 10:39:50 -0500, Matt Sicker wrote: > >> I can't find that package on debian's package search page. >> > >

Re: Github usage

On Thu, 15 Mar 2018 10:39:50 -0500, Matt Sicker wrote: I can't find that package on debian's package search page. https://packages.debian.org/stretch/git-hub I'm not sure if they package it there There is a slew of golang-related packages. (it's a go program, so it's pretty easy to

Re: Github usage

I can't find that package on debian's package search page. I'm not sure if they package it there (it's a go program, so it's pretty easy to install if you have go already). Here's the official site: https://hub.github.com/ On 15 March 2018 at 10:19, Gilles wrote: >

Re: Github usage

Hi. On Wed, 14 Mar 2018 11:27:38 -0500, Matt Sicker wrote: When you have a GitHub origin, you can checkout pulls/42/head to check out PR#42. You can pull/merge from that branch as well to merge the PR (by committing and pushing that merge, GitHub will notice and mark the PR as merged). You

Re: Github usage

When you have a GitHub origin, you can checkout pulls/42/head to check out PR#42. You can pull/merge from that branch as well to merge the PR (by committing and pushing that merge, GitHub will notice and mark the PR as merged). You can also use the "hub" command line tool that GitHub publishes

Re: Github usage

Hi. On Wed, 14 Mar 2018 14:16:42 +, Otto Fowler wrote: I should be more specific, this is for looking at github pr’s. So if your submitters are forking, submitting prs on github. We also have scripts for committing, but we are doing git -> github mirror My knowledge of "git" is small;

Re: Github usage Was: [Statistics] Port codes from Commons Math

I should be more specific, this is for looking at github pr’s. So if your submitters are forking, submitting prs on github. We also have scripts for committing, but we are doing git -> github mirror On March 14, 2018 at 10:15:04, Otto Fowler (ottobackwa...@gmail.com) wrote: We have script to

Re: Github usage Was: [Statistics] Port codes from Commons Math

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

Re: Github usage Was: [Statistics] Port codes from Commons Math

On Tue, 13 Mar 2018 11:43:17 -0400, ajs6f wrote: On Mar 13, 2018, at 11:20 AM, Gilles 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

Github usage Was: [Statistics] Port codes from Commons Math

> On Mar 13, 2018, at 11:20 AM, Gilles 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