Thanks Nate, that's really useful info and Hub makes it easy to get at other folk's repos/forks of Juju to really collaborate, look at code that's WIP and such.
I highly recommend folks take a peek and see how it can improve their collaboration and workflows. Especially when reviewing and QA'ing pull requests from folks. On Tue, Aug 2, 2016 at 12:08 PM Nate Finch <[email protected]> wrote: > I've mentioned this before, but with some of our new code review > guidelines, I figured it's good to reiterate. Github has a CLI tool that > helps with doing git-related things with github. It's called hub. It's > written in Go, so installing it is as easy as go get github.com/github/hub > > Github recommends making an alias to have hub replace git, since it > forwards everything to git that it doesn't understand. Honestly, I don't > really see any benefit to that. I prefer to understand what git is doing > versus what hub is doing. > > It can do a whole bunch of stuff, but there are two things I use it for > the most - checking out PRs and making PRs. > > Since we're supposed to be doing manual testing on people's PRs when we > review them, we need a way to do that. With hub it's one command: > > hub checkout <url of PR> > > so, for example: > > hub checkout https://github.com/juju/juju/pull/5915 > > Bam, your local branch is set to a copy of the PR (don't forget to run > godeps). > > To make a PR from the CLI using hub, make sure the repo you want to PR > against is the git remote called origin, then you can make a PR with your > current branch by just doing > > hub pull-request > > This will open an editor to write the PR message, or you can use -m just > like with git commit. > > -Nate > -- > Juju-dev mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju-dev >
-- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
