Git Commits introduce changes to the codebases that take time and effort to understand and evaluate. Unless the author provides quality information about the scope of the changes, reasons behind them, and the point and purpose, the commit is almost useless.

I'd like to share with you my experience with git commit messages, pull requests, and code reviews, trying to explain how you can save yourself and other time and effort down the line.

Comments

Comments are closed.

Miro Svrtan at 09:51 on 28 Jan 2019

As somebody who has been in the industry for a long time, very aware of how much my commit messages need improvement, even knowing how to do it, I have failed on numerous occassions in forcing my self to improve a lot on this part. Since this talk (7 days ago) I'we started giving lot more care on how I message my changes.

Speaker was really good and motivating (at least for me but would love to see if others were influenced as well), had covered the topic very well.

For 5*:
- interact bit more with audience
- give bit more of personal experience into it

As this was speakers first public talk, I would not take this *suggestions* too harshly and I hope to see him sharing his knowledge even more with the audience!

Bravo Tomo!

Ante Tomas at 20:39 on 29 Jan 2019

Very useful insight into something that most of us take for granted and do not question too much. I appreciate the different perspective that the speaker shared with us and will try to take it into account while I write my commit messages.

As for the stars...let's leave some space for speaker's next talk. :)

Mario Blažek at 15:18 on 15 Feb 2019

Liked the talk very much, Tomo is an outstanding speaker, would love to hear more speeches from him.

Using "If applied, this commit will" from that day on.

Petar Gabud at 21:56 on 18 Feb 2019

Very useful talk for me as mid level git user.
Maybe you should add more Q&A parts to get more interaction with audience.
Last few weeks i write messages by your suggestion :)

Although I stumbled upon a few articles about this before and am already using that approach
(not 100% effective, but still trying to fully integrate it into my workflow), I picked a few neat things from his talk.

I agree with Miro. A little more spark is needed with the audience, but considering this was his first talk,
I'll give him five stars, as I think he'll definitively improve upon this.

If he doesn't, I won't. Think about that for a sec. Yea? Right.

Good job Wrap!