Jose Lopes jose-lopes

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

	#!/usr/bin/env python
	"""Use inotify to watch a directory and execute a command on file change.

	Watch for any file change below current directory (using inotify via pyinotify)
	and execute the given command on file change.

	Just using inotify-tools `while inotifywait -r -e close_write .; do something; done`
	has many issues which are fixed by this tools:
	* If your editor creates a backup before writing the file, it'll trigger multiple times.
	* If your directory structure is deep, it'll have to reinitialize inotify after each change.

	#!/usr/bin/env python
	"""Use inotify to watch a directory and execute a command on file change.

	Watch for any file change below current directory (using inotify via pyinotify)
	and execute the given command on file change.

	Just using inotify-tools `while inotifywait -r -e close_write .; do something; done`
	has many issues which are fixed by this tools:
	* If your editor creates a backup before writing the file, it'll trigger multiple times.
	* If your directory structure is deep, it'll have to reinitialize inotify after each change.