Tom ttntm

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

	// Licensed under a CC0 1.0 Universal (CC0 1.0) Public Domain Dedication
	// http://creativecommons.org/publicdomain/zero/1.0/

	// HTML files: try the network first, then the cache.
	// Other files: try the cache first, then the network.
	// Both: cache a fresh version if possible.
	// (beware: the cache will grow and grow; there's no cleanup)

	const cacheName = 'files';

	# Terminal Cheat Sheet

	pwd # print working directory
	ls # list files in directory
	cd # change directory
	~ # home directory
	.. # up one directory
	- # previous working directory
	help # get help
	-h # get help