Blogging in Lisp


Comitting to a GitHub Pull Request Branch

Submitted by Bill St. Clair on Fri, 09 Oct 2015 09:14:42 GMT

A GitHub pull request submits a branch of a fork of a repository back to the repository it came from. I've wondered about a line on that page:

Add more commits by pushing to the master branch on [forked repository].

So I did an experiment. I created the billstclair/pull-request-repository with only a README in it. I forked that repository to riak-wws/pull-request-experiment, I committed a change to the fork and created a pull request. I committed another change to the fork. That change, as hinted by the quoted line above, also showed up in the pull request.

This is convenient for fixing problems with pull requests, but the take-away for me is that if I expect to do work in a fork with a pull request that is NOT part of the pull request, I should make a new branch just for the pull request.

Add comment   Edit post   Add post

Previous Posts:

Controlling Rebar3 Application Compile Order
Universal Crypto Keychains
mod_spdy with Apache 2.4.7 on Ubuntu 14.04
"stty -echo" in Emacs Shell
Chef Dev Newbie
Kerl Rocks!!
SSL Certificate Added
Mac OS X El Capitan Startup Transients
Ready... Set... Blog...