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

Updated specification

Browse Source
This commit is contained in:
Jim Myhrberg
2017-07-01 14:46:41 +01:00
parent a004e4e3a9
commit 955328a5f2
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
common-flow.md
View File

@@ -46,11 +46,12 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
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 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, "master branch". The master branch MUST always be in a non-broken state, but
meaning it MUST always be in a good enough state that, depending on your MUST be considered to be "bleeding edge". That means the master branch MUST
deployment/release flow, a new release can be built from master, or that always be in a good enough state that, depending on your deployment/release
master can safely be deployed to production. flow, a new release can always be built from master, or that master can
always be safely deployed to production.
2. Changes MUST be performed on a separate branch that SHOULD be referred to as 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 a "change branch". All change branches MUST have descriptive names. You
SHOULD commit locally often, and you MUST regularly push your work to the SHOULD commit often locally, and you MUST regularly push your work to the
same named branch on the remote server. same named branch on the remote server.