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)]

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. I really don’t, you’re a big boy now we’ve let you use big boy tools like the command line take some initiative. It’s 5pm on a Friday before a bank holiday can we release? Wait there’s a gif for this… OK so it’s extreme so here’s the rational slightly less angry and more rational version: