scottdonaldau

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

scottdonaldau

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:

scottdonaldau

Keybase proof

I hereby claim:

• I am scottdonaldau on github.
• I am scottdonald (https://keybase.io/scottdonald) on keybase.
• I have a public key ASCEvC-uHzKcOOPC2n35gCDoAUKW6JteViiAam3Qaag1QQo

To claim this, I am signing this object:

scottdonaldau

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

scottdonaldau

0x6d5c36290E42a9eE6c36B30115186fbf9E9bf074