Journal Archives About Books Talks

Fork you? No, no, no - Fork Queue.

You don't have to be a Dr. Nic with his 100+ public repos to appreciate the Github Fork Queue and how it streamlines accepting patches for your open source projects.

Gittin' picky wi - it

The Fork Queue is a way to cherry pick which pull requests you want to accept, it's not a replacement for your normal git workflow for accepting, testing, and committing patches. If you haven't read Viget's thoughts on patch workflow, head over there and read it first.

The first thing you'll want to do to set up your fork queue is to select or create your integration branch:

The readernaut Fork Queue - GitHub

Simply select an existing branch or create a new one on-the-fly:

The readernaut Fork Queue - GitHub

Once you've done this one-time setup, you can now cherry pick the commits you want to pull into your integration branch:


Once you've accepted or rejected the changes in the queue, you can pull those changes by pulling down that branch:

$ git checkout integration
Switched to branch 'integration'
$ git pull origin integration

Once you've tested and cleanly merged all the changes into your integration branch, flip back to your master branch and merge again.

$ git checkout master
$ git merge integration
$ git push origin master

Forkin' simple.

# Posted on