"Yeah, the movement's in motion with massive militant poetry
Now check this out, uh"

Committing code is an integral part of the development lifecycle, but you just stand there screaming, awaiting the hour of reprisal.

Not all commits or commit messages are created equal. As more data professionals join the crazy train, and are required or expected to use source control within a continuous integration or deployment solution, a lack of good information is reducing the efficacy and usefulness of commit messages, leading to a paranoid symphony of destruction

Whilst it might seem that you are just a stranger to yourself and that commits make you pray for the thunder and the rain to quietly pass you by, its time for a one, two, three, another funky radical bombtrack.

It started as a sketch in my notebook, where we will explore the source control system git, what makes a commit, and what a commit message is for, so that you can paint a picture of days gone by and no longer say holy diver.

We will also learn what makes a good, and a bad, commit message and how to automatically link commit messages to user stories and release notes, ensuring your commits are as legendary as Ozzy and finally you can say So let it be written, So let it be done, I'm sent here by the chosen one.

You will leave this session with a better understanding of commits and commit messages, and useful guidance to make them most effective for yourself and for your team, empowering you to code with hypnotizing power, crushing all that cower. I've gotta say what I've gotta say and then I swear I'll go away.

But I can't promise you'll enjoy the noise.