GitHub Fork and Pull Request Workflow – Quick Reference Guide

README.md

Version 0.1.0 (2018-02-17)

This document describes how developers may contribute pull requests to
an upstream repository and how upstream owners may merge pull requests
from contributors according to the very popular fork and pull request
workflow followed in many projects on GitHub.
The most recent version of this document is available at
https://github.com/susam/gitpr.

Contents
Introduction
Every project has a main development branch where the developers push
commits on a day-to-day basis. Usually, the main development branch is
master but some projects choose to have develop or trunk or
another branch for day-to-day development activities. We refer to this
main development branch as main development branch throughout this
document to keep the text general. However in the command examples and
ASCII-diagrams, we use master as an example of the main development
branch.
Contributors to a project usually develop their contribution in a
feature-specific or bug-specific branch. Usually, such a branch has an
appropriate and meaningful name as per the feature of bug-fix to be
developed. We refer


Original URL: http://feedproxy.google.com/~r/feedsapi/BwPx/~3/_bzbTeZw29w/gitpr

Original article

Proudly powered by WordPress | Theme: Baskerville 2 by Anders Noren.

Up ↑

%d bloggers like this: