Commit Messages I Have Seen

preview_player
Показать описание
Speaker: Billie Thompson

A quick tour of how to to structure commit messages, and what should go in each commit.

This talk is based around real world examples that I have seen, will include 7 quick tips to make your commit messages rock, starting from the basics of how Git and GitHub format your commit message and getting it to display right, all the way through to what tense you should write your commit messages.
  1. Nomad PHP
  2. git
  3. commit messages
  4. php
Рекомендации по теме
Commit Messages I 0:10:12

Commit Messages I Have Seen

What Changed & 0:21:49

What Changed & Why | How to Craft Great Git Commit Messages

Use past tense 0:02:44

Use past tense in git commit messages

git: commit message 0:02:41

git: commit message pro tip (beginner - intermediate) anthony explains #095

Do this to 0:03:00

Do this to fix your Git commit messages (how to reword them)

Change Git Commit 0:04:48

Change Git Commit Messages Tutorial

See MORE of 0:00:34

See MORE of your commit messages at a glance ↕️ 👀 #shorts #programming #git

Your commit messages 0:04:48

Your commit messages suck, time to fix it

♏️ sentimental scorpions 0:22:58

♏️ sentimental scorpions avril 2025.Cette personne se manifeste de façon inattendu !!!

what is git 0:03:38

what is git log and how to see all commit messages with commit id's

When you know 0:00:22

When you know you should add more details to a commit messages #coding #git #humor #shorts

How to exit 0:00:35

How to exit Git Bash commit message window in Windows

#HowICode Commit Messages 0:01:21

#HowICode Commit Messages Best Practice

How to write 0:14:19

How to write BETTER git commit messages?

Oh, everyone can 0:00:06

Oh, everyone can see my commit messages…

How to write 0:00:18

How to write GIT commit messages correctly #businessenglish #englishforprogrammers

How to Ensure 0:01:51

How to Ensure Your commit-msg Hook Only Receives Relevant Commit Messages

Git and GitHub 0:04:59

Git and GitHub - Anatomy of a Commit Message #14

🦾 AI commit 0:00:41

🦾 AI commit message generation for GitKraken Client #chatgpt #openai #git

Git Commit Message 0:07:57

Git Commit Message - You Are Not Doing It Correctly

I review my 0:09:47

I review my old Git commit messages. 🤦‍♂️ These messages are 💩.

backdating git commits 0:03:12

backdating git commits

How to name 0:00:53

How to name your commits #coding #gitclient #git

How to change 0:04:44

How to change Git commit messages (rebase)

Комментарии
Автор

I like discussions about "commit messages", so first thanks for the lightning talk!


And I can really recommand to use a simple prefix ([+], [*], [!], ...) so everybody can easily have a overview in git log.

LarsMoelleken
Автор

Honestly, a lot of this advice is useless. There is no valuable difference between a commit message that ends in a period and one that doesn't.

And I would argue that the imperative mood is the _worst_ way to communicate an action taken in the past. Surely, the simple past tense ("Created a new entity."), or simple present ("Creates a new entity.") would be more readable. You should describe what a commit _did_ or _is doing_, not what a programmer should _have done_. A commit history is the opposite of a to-do list.

TheCoryKid