KlfJoat

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

	.SILENT:
	.PHONY: help

	# Based on https://gist.github.com/prwhite/8168133#comment-1313022

	## This help screen
	help:
	printf "Available targets\n\n"
	awk '/^[a-zA-Z\-\_0-9]+:/ { \
	helpMessage = match(lastLine, /^## (.*)/); \

	import pytumblr
	import os
	import code
	import oauth2 as oauth
	from pprint import pprint
	import json
	import urllib
	import codecs

	# Number of likes to fetch in one request

	# Add the following 'help' target to your Makefile
	# And add help text after each target name starting with '\#\#'

	help: ## Show this help.
	@fgrep -h "##" $(MAKEFILE_LIST) \| fgrep -v fgrep \| sed -e 's/\\$$//' \| sed -e 's/##//'

	# Everything below is an example

	target00: ## This message will show up when typing 'make help'
	@echo does nothing

	NAME=project
	VERSION=0.0.1

	DIRS=etc lib bin sbin share
	INSTALL_DIRS=`find $(DIRS) -type d 2>/dev/null`
	INSTALL_FILES=`find $(DIRS) -type f 2>/dev/null`
	DOC_FILES=.md .txt

	PKG_DIR=pkg
	PKG_NAME=$(NAME)-$(VERSION)