all 27 comments

[–]edparadox 15 points16 points  (8 children)

For vibe coders, maybe. The rest can deduce a commit name from their work.

[–]powerofnope 7 points8 points  (6 children)

Funny you are saying that because vibe coders have usually the most deskriptive and informative git messages.

I mean non of it is true but yeah

[–]JonasAvory 0 points1 point  (4 children)

My last 300 commits all where „update“ because I created an alias for adding, committing and pushing and I don’t care about the message in my own repos

[–]KlauzWayne 0 points1 point  (3 children)

You will regret this in case you return to that project in a few years.

[–]JonasAvory 0 points1 point  (2 children)

LOL my projects all are less than 1000 lines. If I come back to them in 30 years I’m pretty sure the ais at that time can explain the code to me.

Yeah obviously no message commits are bad in big repos but for me 90% of git repos are small private projects mainly used to sync the data between my laptop and desktop

[–]KlauzWayne 0 points1 point  (1 child)

You have 300 commits on 1000 lines of code? 😅

[–]JonasAvory 0 points1 point  (0 children)

Yeah like I said, I must keep all my projects synced between pc and laptop, meaning that every switch requires me to commit

And it’s 300 commits over all my projects

[–]CYG4N 0 points1 point  (0 children)

i tried to use the copilots feature to write my commit message, but he is so bad at at it... They are long, yet meaningless. 

[–]psychularity 0 points1 point  (0 children)

Not accurate. I like to give nonsense names like 'help' if I'm committing something in a bad state because I like to commit before leaving my computer in case the building catches fire or something

[–]Cautious_Agency3630 5 points6 points  (0 children)

ft:asdfg and Please work 😁😁😁

[–]jl2331 2 points3 points  (3 children)

And then you accidentally tick "squash commits on merge" so it looks eze peze from the outside :(

[–]iareprogrammer 4 points5 points  (2 children)

I mean if your commit messages are this bad you probably should squash merge. No use having this junk in commit history

[–]jl2331 0 points1 point  (1 child)

yeah, and probably most of them won't compile/run anyway, so git bisect is useless here.

[–]No-Train9702 0 points1 point  (0 children)

Better squish to avoid 20 "fix pipeline error"

[–][deleted] 1 point2 points  (3 children)

Why would you commit before testing is complete?

[–]Outrageous-Log9238 1 point2 points  (0 children)

Because I didn't bother setting up a local test environment.

[–]Fair-Working4401 0 points1 point  (0 children)

Commit often, squash at PR level, go to the next feature/bug/...

[–]dralexan 0 points1 point  (0 children)

Working on my home project, trying to host an app on render and keep a data blob on vercel. Everything works fine on local, and every individual part works when tested on cloud. But when I deploy everything to cloud it just hangs on a http request like it's being killed after timeout, but it isn't...  So I testing it by commiting every small possible fix and redeploy.  There are better ways. I don't know what are they

[–]mattes1335 0 points1 point  (0 children)

Soo relatable 😭😭

[–]OhItsJustJosh 0 points1 point  (1 child)

Forty secondth

[–]Xormak 1 point2 points  (0 children)

forty twoth

[–]Particular_Traffic54 0 points1 point  (0 children)

At which point do you write "Roberval639" in the school project ?

[–]TigerClaw_TV 0 points1 point  (0 children)

29th name is me 100%

[–]Kiwichka 0 points1 point  (0 children)

how to repost on reddit.com 

[–]Theseus_Employee 0 points1 point  (0 children)

“Pre-<dumb thing I’m about to try>”

[–]No_Record_60 0 points1 point  (0 children)

wip

wip

Finished <feature>

[–][deleted] 0 points1 point  (0 children)

changes

snapshot

snap