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 Common-Flow vs GitHub Flow FAQ question

Browse Source
This commit is contained in:
Jim Myhrberg
2017-08-26 23:19:54 +01:00
parent 927a00a7bd
commit 68e0502dac
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
common-flow.md
View File

@@ -268,6 +268,22 @@ In detail, the main differences between Git Flow and Common-Flow are:
branches when it makes things easier. If creating a new release by tagging branches when it makes things easier. If creating a new release by tagging
"master" works for you, great, do that. "master" works for you, great, do that.
**Why use Common-Flow instead of GitHub Flow, and how does it differ?**
Common-Flow is essentially GitHub Flow with the addition of a "Release" concept
that uses tags. It also attempts to define how certain common tasks are done,
like updating change/feature branches from their source branches for
example. This is to help end arguments about how such things are done.
If a deployment/release for you is just getting the latest code in the master
branch out, without caring about bumping version numbers or anything, then
GitHub Flow is a good fit for you, and you probably don't need the extras of
Common-Flow.
However if your deployments/releases have specific version numbers, then
Common-Flow gives you a simple set of rules of how to create and manage
releases, on top of what GitHub Flow already does.
**What does "descriptive name" mean in terms of change branches?** **What does "descriptive name" mean in terms of change branches?**
[answer goes here] [answer goes here]