Skip to content

Instantly share code, notes, and snippets.

View rishacha's full-sized avatar
💭
I may be slow to respond.

Rishabh Chakrabarti rishacha

💭
I may be slow to respond.
View GitHub Profile
@rishacha
rishacha / GitHub-Forking.md
Last active March 21, 2019 10:06 — forked from Chaser324/GitHub-Forking.md
GitHub Standard Forking and PR Workflow

Introduction

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.

Commit message workflow

For committing to any project, it's necessary to create a well-thought commit message template. This template should tell you all about the `CHAN