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

fix(links): update link URLs

Browse Source 
Update links to newer URLs, so they no longer point to dead URLs.
This commit is contained in:
Jim Myhrberg
2026-01-10 18:23:59 +00:00
parent f1eae76bd0
commit c471aa9b37
1 changed files with 7 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
common-flow.md
View File

@@ -6,9 +6,10 @@ Introduction
Common-Flow is an attempt to gather a sensible selection of the most common Common-Flow is an attempt to gather a sensible selection of the most common
usage patterns of git into a single and concise specification. It is based on usage patterns of git into a single and concise specification. It is based on
the [original variant](http://scottchacon.com/2011/08/31/github-flow.html) of the [original variant](https://scottchacon.com/2011/08/31/github-flow/) of
[GitHub Flow](https://guides.github.com/introduction/flow/), while taking into [GitHub Flow](https://docs.github.com/en/get-started/using-github/github-flow),
account how a lot of open source projects most commonly use git. while taking into account how a lot of open source projects most commonly use
git.
In short, Common-Flow is essentially GitHub Flow with the addition of versioned In short, Common-Flow is essentially GitHub Flow with the addition of versioned
releases, optional release branches, and without the requirement to deploy to releases, optional release branches, and without the requirement to deploy to
@@ -21,7 +22,7 @@ Summary
broken. broken.
- Changes (features, bugfixes, etc.) are done on "change branches" created from - Changes (features, bugfixes, etc.) are done on "change branches" created from
the main branch. the main branch.
- Rebase change branches [early and often](https://i.imgur.com/1RS8x2d.png). - Rebase change branches early and often.
- When a change branch is stable and ready, it is merged back in to main. - When a change branch is stable and ready, it is merged back in to main.
- A release is just a git tag who's name is the exact release version string - A release is just a git tag who's name is the exact release version string
(e.g. "2.11.4"). (e.g. "2.11.4").
@@ -53,7 +54,8 @@ 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://datatracker.ietf.org/doc/html/rfc2119).
1. TL;DR 1. TL;DR
1. Do not break the main branch. 1. Do not break the main branch.