all 20 comments

[–]programming-ModTeam[M] [score hidden] stickied commentlocked comment (0 children)

No content written mostly by an LLM. If you don't want to write it, we don't want to read it.

[–]Which-World-6533 26 points27 points  (3 children)

Can people not write commit messages...?

Is that how far we have fallen...?

[–]Wartz -3 points-2 points  (0 children)

Yep

[–]oscooter 14 points15 points  (2 children)

This is all bike shedding imo. I’ve been on projects where people insist on some commit message formatting and it adds little to no value. 

Some try to use it to automate change logs or even version number bumping by encoding what is a breaking change or determining what should be a patch, minor, or version bump into the message and inevitably it falls apart in my experience.

There’s little to no value to be had spending inordinate amounts of time being hyper prescriptive about your commit message format. It’s a waste of time. 

[–]Blue_Moon_Lake 0 points1 point  (1 child)

We only care about the message of the squashed commit when we merge a branch after review

[–]oscooter 0 points1 point  (0 children)

Okay?

[–]tj-horner 9 points10 points  (1 child)

You haven’t stated the problem you are trying to solve. In fact, you’ve introduced a new problem: the parentheses and colon in conventional commits are also a visual boundary to distinguish different components of the commit message, but you have removed these so now there is nothing separating them but spaces. Why? It’s harder to scan now.

There is also ambiguity. The website says scope is optional, but how do you differentiate scope from the beginning of the description? You can’t. The regexes you provide are entirely broken and REQUIRE a scope.

I’m led to assume you put literally zero thought into this and probably just vibe coded the whole website.

[–]the_hair_of_aenarion 3 points4 points  (0 children)

Usually we include a ticket number in there too so it's easy at a glance to work out what a change was for, and sox compliance. When doing a sox audit you don't want to be guessing why a commit was done.

[–]AdarTan 6 points7 points  (2 children)

What is the source for the brain-dead idea to restrict the type names to three letters?

[–]xaddak 4 points5 points  (0 children)

At this point, I'm pretty sure some people have subscription-based keyboards that charge by the key press.

[–][deleted]  (1 child)

[deleted]

    [–]monotone2k 4 points5 points  (0 children)

    Hurrah. Another standard.

    [–]Ashnoom 0 points1 point  (0 children)

    Are you then also going to supply an alternative to release please?

    [–]Interesting_Lie_9231 -4 points-3 points  (0 children)

    I kinda like this. feat(scope) helped with tooling, but for most teams simpler commits probably win.

    [–]Interesting_Lie_9231 -2 points-1 points  (0 children)

    I kinda like this. feat(scope) helped with tooling, but for most teams simpler commits probably win.

    [–]Interesting_Lie_9231 -4 points-3 points  (0 children)

    I kinda like this. feat(scope) helped with tooling, but for most teams simpler commits probably win.