Git

Since we have git flow as a nice standard it makes sense to standardise our commit messages as well. Here’s the following proposed standard: [Updated | Added | Removed (required)] [Component (required)] [Reason] - [Issue Reference (required)] Action - Updated/Added/Removed - Three options to concisely describe what this commit achieves. If your commit message doesn’t fit any of the words then you might want to reconsider splitting the commit up into smaller chunks (git add -p)....

Here is an unedited version of the post. Raw and uncensored: After many a fruitless and frustrating discussions around git best practices here’s my bulletproof method: Tag it - if you want to release code you have to tag it. By tagging you also own that release if it doesn’t fucking work I’ll hunt you down. You did test it, right? What branch should I use? I don’t give a shit....