Learn to write good commit message and description

[webknjaz]

According to common commit style guides, it is required to write messages in an imperative manner. Make them actionable. Also avoid using -m as you often need to express more detail in a long way. Here's several articles sharing best practices:

• [x] http://chris.beams.io/posts/git-commit/
• [x] http://alistapart.com/article/the-art-of-the-commit
• [x] https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message
• [x] https://github.com/erlang/otp/wiki/writing-good-commit-messages
• [x] https://wiki.openstack.org/wiki/GitCommitMessages
• [x] http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
• [x] https://dev.to/gonedark/when-to-make-a-git-commit
• [x] https://seesparkbox.com/foundry/atomic_commits_with_git
• [ ] https://twitter.com/nedbat/status/1283147492616556544
• [ ] https://dhwthompson.com/2019/my-favourite-git-commit Please read at all of them :)

N.B. This all applies to issues and PRs.

[webknjaz]

@RootenberG now apply the above principles to all of your commits and maybe rewrite Git history of the branch bound to https://github.com/kpi-web-guild/devspace/pull/6. Please also use the same style when creating issues and PRs on GitHub.

[webknjaz]

@RootenberG I think that you need to re-read the commit recommendations mindfully once more.