James Carlos jamescarlos

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, when I started going through the process of forking and issuing pull requests, I had some trouble figuring out the proper method for doing so and made quite a few mistakes along the way. 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

	<?php
	class Post
	{
	protected $table = 'posts';

	/**
	* You can define your own custom boot method.
	*
	* @return void
	**/

	#!/bin/bash

	#--------------------------------------------------------------------
	#
	# can put this in your .bashrc or .zshrc
	# if [ -f ~/.git_bash_functions ]; then
	# . ~/.git_bash_functions
	# fi
	#
	#--------------------------------------------------------------------

	# ~/.bashrc: executed by bash(1) for non-login shells.
	# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
	# for examples

	# If not running interactively, don't do anything
	[ -z "$PS1" ] && return

	# don't put duplicate lines in the history. See bash(1) for more options
	# ... or force ignoredups and ignorespace
	HISTCONTROL=ignoredups:ignorespace

	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console