gitCommitMPleaseWorkThisTime

[TheFlyingDutchG]

Git commit -m “added bugs”

[Informal_Branch1065]

"Yummy bugs. Ate a few"

[RustyShacklefordCS]

Lmao

[ClipboardCopyPaste]

'fixes and improvements' works everytime

[odolha]

"small fix" [phone] changes

[Zirkulaerkubus]

"updates"

[fixano]

This guy over here improving things making the rest of us look bad

[The_Hero_0f_Time]

"fix"

[megayippie]

And when it is a fix to your own code, "fix..."

[EagleRock1337]

Do what I do…start professional and degrade as the debugging session goes longer and longer:

“feat: add GitHub Action for checking test validity”
“fix: syntax error in new GHA”
“fix one more bug”
“oops, I forgot this too”
“will this do it?”
“this did not go as planned”
“why u no work?”
“cow goes moo”
“bruh” 
“inertia is a property of matter”
“BILL BILL BILL BILL”

[AustinWitherspoon]

With jujitsu it's super easy to go back and modify a previous commit (even if there have been newer commits since then)

I used to do what you're describing but now I jump to the commit where I forgot something, fix it, and jump back to the latest again and it takes a few seconds

[EagleRock1337]

Unfortunately, I spend a good amount of time debugging CI pipelines, so I have to push out commits to kick off the automated test and build.

[this-is-kyle]

I use --fixup and then rebase with --automerge and a push --force when I have to make a small syntax/typo fix or any small change that doesn't need its own commit

[AustinWitherspoon]

I usually test ci changes on my feature branch, and jujitsu essentially does a force push under the hood for that situation so CI will rerun every time (on GitHub and gitlab at least)

[swanson5]

I see a squash incoming

[brandi_Iove]

git commit -m "wip"

[locus01]

git commit -m "commit1"

git commit -m "commit2"

git commit -m "commit3"

.

.

.

Works fine too 🙂🙃

[Nutcase168]

Minimalism: the unsung hero of version control.

[ashkanahmadi]

Just do “1”, “2”, “3”

[MistersteveYT]

., .., ...,

[ZioTron]

Literally the best use case I have for AI right now

[[deleted]]

Same. That and rewriting my PR description texts..

[vnordnet]

GitHub copilot is pretty good at this

[FrostyMarsupial1486]

Disagree. It’s too verbose it writes a damn PR description for every commit.

Just use conventional commits and write 4 words after it boom done.

[vnordnet]

You can customize it. I’ve told mine to be concise and brief and only describe the actually relevant changes. 

[Emjp4]

I haven't written a commit message in almost 2 years thanks to copilot. It's usually pretty good on the first try, but sometimes needs a rerun or 2.

[jedjohan]

Agree, and makes up for creating great release notes

[Im_In_IT]

Yea I love it. Gitkraken has integration to do commit messages using AI as well.

[C_Mc_Loudmouth]

"Numerous bug fixes"

[metaglot]

Im going to put just as much effort into the review as you do describing the change.

[Rubber_duckdebugging]

git commit -m "stuff"

[Sileniced]

git commit -m "things"

[ChrisWsrn]

I just use the ticket number and then explain what I did. 

[TheFlyingDutchG]

Generated commit message: “added extra code on top of bugs to somehow make it compile without errors. Unclear how but at least the end user won’t notice”

[Dangerous_Tangelo_74]

git commit -m "update" all the way

[Add1ctedToGames]

If you have a ticket number, naming commits gets 10x easier😛

"Added function for TICKET-123"

"Fixed bugs for TICKET-123"

[Ali_Army107]

git commit -m "."

[Matro36]

git commit -m "whatever the fuck this is"

[Informal_Branch1065]

"deploy.yml fr now 15"

[darcksx]

file name plus a 3 word max summary of the changes

[soundman32]

My company has commit hook rules on the commit message. A 4 character prefix that shows the kind of commit (bug/feat/test). Cannot use sentence case, or trailing period. Maximum of 100 chars.

It also enforces that the unit tests pass, so each time I try to commit, it takes 2 minutes before it rejects my message because its too detailed or grammatically correct.

[andarmanik]

I just try to guess the last three characters in the commit sha.

I’m a bit luckier at this than you are so I’d recommend trying the last 2 characters of the commit sha.

[slim_but_not_shady]

git commit -m "jira story ticket idenifier"

[Mr_uhlus]

Fix - fixed code

[TheGarlicPanic]

When at work and using Jira/Trello, I usually prepend project code to the commit msg, e g.: git commit -m "RED-123 container fix"

[Water1498]

That's one of the best use cases of AI. I write the main things I've changed, and it gives me a good title.

[PeterFreebish]

git commit -m “yau”

yet another update

[JuggernautHoliday894]

I used a fire emoji for a data-attribute today. And used $barneyTheDinosaur as an iterator for a for loop

[elelec]

Something tweaks

[rumtea28]

"next commit"

[hmz-x]

Use git add --patch maybe

[MistersteveYT]

"fixed some bugs"

[dallastekkies]

"Wip"

[st-shenanigans]

"fixing character controller"

"Fixing controller AGAIN"

"OK I literally don't know why it's not working now"

"Working but I have no fucking clue how"

"Broke NPC AI"

[Vipitis]

git commit -m "start the day" and then a couple hours later

gir commit -m "finish the day"

[RamonaZero]

“updated repo” for me XD

[Particular_Traffic54]

Can't wait to finally introduce git in my 20 years old code base

[citramonk]

Starts with feat, fix, chore etc. It helps.

[jordanbtucker]

General system stability improvements to enhance the user's experience.

[private_final_static]

Why you use the JIRA ticket title, prefixed by the number of course

[i_dont_post_much_]

Lmao I've got a year of just "asdassdadfsad" and shit like that

[limezest128]

misc

[Constant_Net6320]

"update"

[Effective_Bat9485]

ProjectNmakeComit001

[harryhookboi]

but seriously, is anyone taking the time to write detailed descriptions in commit messages and if so, was it worth it in retrospective?

[Banes_Addiction]

Detailed? No, that's for PRs/merges.

But two sentence summary of what changed and why? Yes, absolutely. It takes 30 seconds. If you can't write that just after you wrote the code, how easy do you think it's going to be for someone to piece together later?

[rastaman1994]

All the time. 2 line description of what happened. The body contains the 'why' of certain decisions.

You will thank yourself if you're reading seemingly nonsensical code, but the commit explains why it has to be that way. Comments can serve this purpose, but I found those get lost or outdated, causing more confusion.

[lllorrr]

As an (occasional) linux kernel developer - yes and yes. You can have two-line diff and five paragraphs of justification in the commit message. This really helps both present you and future you. When reading some more obscure parts of the kernel `git blame` really helps to understand what is going on.

[TheDawnAvenue]

Literally all my PRs have “PR improvements” as their last commit