Git Process by pinage404

Table of Content:

• How it has been done ?
• How to improve it ?
• Inspirational resources
• Licence

How it has been done ?

• The diagrams are generated by PlantUML
• The site are generated by Jekyll & SASS
• The style is reseted by Normalize via a CDN
• The repository & the site are hosted by GitLab using GitLab CI
  • TIP: Don’t confuse cache and artifacts the documentation is not really clear
• The site is tracked by Google Analytics

How to improve it ?

• @TODO:
  • Try to use the following plugins:
    • jekyll-autoprefixer
    • pug-jekyll-plugin
    • jekyll-babel
  • Add: polyfills
  • Add: commit rules
  • Add: diagrams’ description
  • “How should be managed small / unique commit ?” a branch is a bit too much but this respects the process ; this forces to create a “bin branch” with many small commits with relations between ; IMO this is not a good method but i don’t know how to handle it better yet
  • Upd: improve the “tooltip” behavior on the diagram links
  • Add: git tag in diagrams
  • Add: fix branches in diagrams
  • git log Refacto Loop add git reset --hard if this is a mess
  • Add: update branch name if needed
• @FIXME:
  • menu links
  • SVG render on phone (Chrome Android & Firefox Linux)
  • zoom on phone (Chrome Android)
  • tooltips must be displayed before the image is downloaded

Inspirational resources

• The flow described in GitLab Review
• The Git Flow Cheatsheet
• The branching model of A Successful Git Branch Model
• The AVH version of Git Flow (used in Debian repository)

Licence

Licence