this post was submitted on 27 Jul 2023
37 points (100.0% liked)

Git

2888 readers
1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago
MODERATORS
Ategon@programming.dev
jnovinger@programming.dev
canpolat@programming.dev
37
What's your commit message style? (programming.dev)
submitted 1 year ago by canpolat@programming.dev to c/git@programming.dev
19 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.sdf.org/post/1352760

Was digging through a project at work today where some guy in 2014 made 100+ commits in a single day and the only one that had a comment said "upgrading to v4.0".

you are viewing a single comment's thread
view the rest of the comments
[–] sucks_syntax@programming.dev 3 points 1 year ago (1 children)

We have a monorepo with multiple websites and applications, we also use azure DevOps. Our commit messages are formatted like this: {website/application} - {feature} - {brief description} - {#work item} so e.g. "Auth - MFA - auto focus login field #162589"

The most beneficial part is the work item number, being able to link the code changes directly to the business logic is huge.

Also beneficial for bug fixes, push the commit with the bug id and the code changes are linked on the ticket automatically.

[–] tuna_casserole@programming.dev 1 points 1 year ago

Oh I like the work item number idea. We've been putting in a line to explain why the change is being made. Being able to link directly to a card or something is noice.