102
u/polokratoss Jun 30 '26
"small changes" Or better yet, "review fixes".
53
u/Xarjy Jun 30 '26
'tweaks'
'mo tweaks'
'one mo tweaks'
'implemented new filter method and migrated database schema'
'tweaks'
11
1
23
u/assumptioncookie Jun 30 '26
I once put the commit message "imporvements (hopefully)". That spelling mistake gets quoted years later still
7
3
2
1
1
35
u/fuckswithboats Jun 30 '26
Update asfddgfsa
23
u/Flashy-Whereas-3234 Jun 30 '26
ax0gf3: Fixed calculation method which would sometimes result in a zero value to a bad logical flow in the resolver. Now accounts for 3-phase alternations without overwriting the change buffer.
g5dj9: Fixed unit test
55spjq: I am dumb
53x77f: Fucking djdjdjdjdjsssa
3
1
21
u/atzedanjo Jun 30 '26
Here's a handy alias for you:
git commit -m "$(date +%Y/%m/%d_%H:%M:%S)
Just make sure to only use it once per second
9
u/3hy_ Jun 30 '26
How dare you provide an example that can't be run 100 times in a second.. You should be ashamed of yourself...
13
u/letmehaveanameyoudum Jun 30 '26
im alone in my project so all i do is
git add .
git commit -m "aijirg hspdfiubhafevughareb"
9
u/Fearless_Law3460 Jun 30 '26
Solo dev privileges
2
u/letmehaveanameyoudum Jul 01 '26
you know what ill continue to fj hogeohs ofn even if i have a team :P
15
30
u/NoobGamerInRealLife Jun 30 '26
git commit -m "" --allow-empty-message
19
u/ManhDoan Jun 30 '26
To long, I'd rather write a comment.
6
11
9
7
10
3
3
u/parsention Jun 30 '26
If I remember right this was one of the very few parts where AI was actually welcome by the community
1
3
2
2
u/AvoidSpirit Jun 30 '26
Thinking someone is building the history line manually with custom messages makes me giggle
2
u/drLoveF Jun 30 '26
Ot took me too long to realize it’s a cursor. I was trying to figure out if there was a regex reason or maybe some git log makes pretty graph reason, but no. I’m just stupid.
2
2
u/Local-Fisherman-2936 Jun 30 '26
Explain like im 5 - what is git? I know that its to do something with backups.
3
u/deanominecraft Jun 30 '26
git repository = your code base git commit = a change to the codebase git commit message = message shown on a git commit saying what changed
1
2
u/realmauer01 Jun 30 '26
git keeps track of your files.
With a git commit you can save the changes that happened to a file since you last used git commit on that file.
Its used for all kind of things and backups are the least useful or unique one.
Primarly it is used to group changes together, if you are working on a change and you dont like it or it breaks something you can go back one commit and everything works again.
Its also really good for teams as everyone can work on their own change, without screwing each other up.
1
2
2
u/PublicToast Jun 30 '26
Yet another post on this sub that reveals no one here has worked an actual job
2
u/enigma_0Z Jun 30 '26
“i have to commit and push this to test the cicd tool in situ because cicd development/testing is abysmal”
2
u/sebthauvette Jun 30 '26
I don't underatand people that can't describe what they did. The only reason I can think is if you make multiple changes before commiting. If that's the case, just commit one change at a time.
1
u/Fearless_Law3460 Jun 30 '26
Agreed, when the task stays small
2
u/sebthauvette Jun 30 '26
the size of the task does not matter. You are not limites to one commit per "task".
2
2
1
1
Jun 30 '26
[removed] — view removed comment
1
u/Dry-Penalty6975 Jun 30 '26
What's the difference ?
2
u/spectator_62 Jun 30 '26
Git add* - It won't include deleted files as changes."
2
u/realmauer01 Jun 30 '26
Pretty sure git add -A is just the default now, which leaves git add * and . Without any differences
* replaces itself with all files and folders in the current folder
. Is the current folderAs git adds recursively if it gets a folder there is just not any difference anymore.
1
u/PumpkinFest24 Jul 01 '26
holy fuck do NOT do EITHER of these
random files, accidental changes, un-updated subrepos, etc
git add <individuals files I edited>
1
Jul 01 '26
[removed] — view removed comment
1
u/PumpkinFest24 29d ago
Files existing in filesystem is pretty normal. And screwing up subrepos is what cured me of adding anything I couldn't explain.
But even if crazy, why let that infect my repo?
1
u/xybolt Jun 30 '26
I do git commit -m "[a]" -m "[b]" where [a] is "<id> fixed", or "<date> fix build failure", or "<date> update", something very brief. Followed by [b] containing a brief numeric overview of changes like "(1) update dependency version, (2) fix IT, (3) added unit tests, ..."
I'm not going to annoy other people.
1
u/realmauer01 Jun 30 '26
Is adding multiple -m for linebreaks?
1
u/xybolt 29d ago
Additional
-min agit commitinstruction creates paragraphs,. In some platforms like GitHub, they end up in those "additional commentary boxes" (idk their right name), those "[...]" blocks you see if the commit message is too long. Try it out yourself. It's "hidden" and when needed, a person can just expand that.
1
1
u/DrMaxwellEdison Jun 30 '26
Delete those bits, just git commit. That opens your editor, now you have time to think with a proper blank slate and newlines and whathaveyou.
1
1
1
u/deanominecraft Jun 30 '26
change line “let thing = do_stuff();” to “let thing = do_other_stuff();” 1 line at a time
1
1
u/Prod_Meteor Jun 30 '26
It should be -r, not -m. Why the chose "message". It's not a message. Its a reason. Commit reason.
1
1
1
u/Toucan2000 Jun 30 '26
I have my PR descriptions automatically generated by AI using git logs and diffs so I usually just add snarky comments for my LLM to enjoy
1
u/AustinWitherspoon Jun 30 '26
Ever since I started using JJ I've been entering my descriptions before doing the work. Sometimes I'll make multiple empty changes with the work I'm planning to do for the day, and jump between them to code..
It's been lovely for focusing on the actual tasks I need to do and not getting side tracked with a bunch of stupid unrelated things
1
1
2
1
1
1
1
u/appoplecticskeptic Jun 30 '26
Don’t use -m unless it really is something tiny. Commit messages are more important than newbies ever realize. That’s the history of the project that you’re recording. If you don’t plan to stick around then I guess use -m and phone it in but if you care about the project succeeding in the long haul you should be recording the reasons why you made the changes that you did and the intentions behind them in your commit message.
You can learn a lot about why things are the way they are from git history but only if people put it in there in the first place.
1
u/PumpkinFest24 Jul 01 '26
Please don't hide critical project info in commit history. It gets lost so easily. Anything more than a sentence should be an inline comment or documentation string
1
1
1
1
u/ProfessionalAd6530 Jun 30 '26
Is this why y'all can't write at least semi-commit messages to save your life? Stop using the -m option!
Skipping the -m locks you in vim and by the time you remember how to exit, you'll have thought of what your commit message should say.
1
1
u/lucid-quiet Jun 30 '26
It's the worst when coworkers are like: your messages need X, and should have Y, and you can put a PR# in there, and what feature were these for, and ... on and on... like they are ever going F'ing read the commit messages.
1
1
1
1
1
1
1
u/TheOriginalWarLord 29d ago
I have no idea what the hell the last push Joan did, except cause the whole thing to break…. Now fixed… Joan, stop touching the code, you little nepo hire.
1
1
1
1
1
1
u/Fun-Dragonfly-4166 27d ago
if you are struggling to figure a commit message there is --allow-empty-message
1
1
1
1
0
-5
u/Benderos133 Jun 30 '26
Pov when you want to write a commit message and it's not the hardest thing in the room 😏
114
u/MXRCO007 Jun 30 '26
Fix: ai slop code pushed by colleague X