Clean repository

[cezarypiatek]

• every project should use repository, event single developer projects (backup, change tracking, ability to revert to given revision)
• working with branching and PR - no more broken code on master
• branch naming
• commit descriptions
  • prefixing
  • comment
  • githook
  • tracking changes with context
  • examples of good and bad commit descriptions
• mixing information from repository with data from issue tracker
• PR description (context)
• TortoiseGIT integration with issue tracker

Splashscreen: https://unsplash.com/search/photos/repository

[cezarypiatek]

https://www.monkeyuser.com/2018/pull-request/