Skip to content

Instantly share code, notes, and snippets.

@insteps
Created March 30, 2020 17:52
Show Gist options
  • Save insteps/7bd63123e195b40b23044596d4e4eced to your computer and use it in GitHub Desktop.
Save insteps/7bd63123e195b40b23044596d4e4eced to your computer and use it in GitHub Desktop.
rfc: alpinelinux gitlab flow v0.0.1
I have been using a similar git-flow for all my codes for sometime now, and have over period of time found it useful.
Following it may not be as easy it seems
Pros
----
1. One has some buffer zone, in event git commits become undesirable and needs reverting.
2. More independant nodes can join without much difficulty.
@insteps
Copy link
Author

insteps commented Apr 4, 2020

Some good practices:

  1. Branch names that are widely used and improves git-flow
    a. dev
    b. features
    c. hotfix
    d. staged
    e. releases/ (used as prefix, so for release version 1.2.3 becomes releases/1.2.x or releases/1.2)
  2. Commit text-prefixes
    Added | Changed | Deprecated | Fixed | Removed | Security
    (could be in small-caps)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment