jimeh/common-flow
1
0
Fork 0
mirror of https://github.com/jimeh/common-flow.git synced 2026-02-19 09:26:40 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add first two clauses to specification

Browse Source
This commit is contained in:
Jim Myhrberg
2017-07-01 14:35:06 +01:00
parent 98b483edb6
commit bf49e2cdb9
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
common-flow.md
View File

@@ -41,3 +41,13 @@ Git Common-Flow Specification (Common-Flow)
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119). interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
1. A branch called "master" MUST exist, and it SHOULD be referred to as the
"master branch". The master branch MUST always be in a non-broken state,
meaning it MUST always be in a good enough state that, depending on your
deployment/release flow, a new release can be built from master, or that
master can safely be deployed to production.
2. Changes MUST be performed on a separate branch that SHOULD be referred to as
a "change branch". All change branches MUST have descriptive names. You
SHOULD commit locally often, and you MUST regularly push your work to the
same named branch on the remote server.