Git: History matters

Git: History matters

0a455056ceebeeefc447d5ba29574e3b?s=128

Michal Těhník

October 24, 2016
Tweet

Transcript

  1. 2.

    Workflow pull request change log remote branch git checkout -b

    prefix/name git checkout master git pull git commit git fetch git rebase origin/master git push origin prefix/name git pull
  2. 5.

    How great commit looks like • Should tell story •

    Don’t tell what did you do, but why • Commit like you commit to Linux Kernel • You should write commit message before implementation • Atomic • External links
  3. 8.

    Actions • introduce new labels ◦ Feature, Improvement, Bug •

    introduce link to productboard • rethink branch prefixes (abandon Git Flow) • be more careful about commits and PR’s • forbid push to the master
  4. 9.

    Resources Git Workflow https://robots.thoughtbot.com/streamline-your-git-workflow-with-aliases How to Write a Git Commit

    Message http://chris.beams.io/posts/git-commit/ Commitizen https://www.npmjs.com/package/commitizen A Tale of Three Trees https://www.infoq.com/presentations/A-Tale-of-Three-Trees FrequencyReducesDifficulty http://martinfowler.com/bliki/FrequencyReducesDifficulty.html