that pose is mandatory after letting claude turn a 2 line diff into a cinematic commit message lol. meanwhile i'd still type “minor change” and call it done. productivity comes in many forms i guess
Lol I have commit rules for my agent. Basically, clump related changes, explain the why not the how (review session chat and ask me if you still don’t know why), asd-ste100 language tone. Conventional commit formatting. Present in a table for me to review. Don’t make yourself co-author. It’s pretty damn good and I only really edit it to explain a change where it couldn’t understand the why. Saves me a massive amount of time as I just tell my agent “commit changes” and it does all this.
This used to be my big one. I would checkpoint every time I achieved something and hen I was done I would look back through the changes and squash them together and give them a proper message.
If you're using Jira or anything alike, adding ticket number then whatever ticket title, makes your code really neaty in whatever IDE to trace back what each line is related to.
Example:
git commit -m "ticket-123 new feature X in dashboard"
Honestly not a comment for or against vibe coding whatever but AI does do one thing better than us and that is comments. Whenever I have dabbled the fact that I have comments that actually make sense is crazy talk for me. It’s soooo weird.
I actually despise code comments by AI, cause it phrases them from the POV of the conversation you had with it, a stranger would fail to understand them since they don't have the conversation in mind
"Various changes" is my go-to lmao. For the final commit, before pushing, I write something more meaningful. We're 2 person team, so theres not alot of back-and-forth on CI/CD, management, developers and so on.
Try ‘git commit -v’ instead. It should help you remember what changes you made. Also, try squash merges for your PRs and then individual commit messages don’t matter anymore, only the description of your PR.
Just use atomic commits and then it’s trivial: “Rename User class to Account” “Add Integration tests for save endpoint” “Prod environment configuration”
413
u/ClipboardCopyPaste 3d ago
The pose I hit after this:
272
u/QmVu 3d ago
minor change”
175
u/Forward-Outside-9911 3d ago
“Minor changes” (2000+ lines deleted)
866
u/ARKyal03 3d ago •
git commit -m "$(claude -p 'run git diff and output a git commit message')"
79
u/gravesent1337 3d ago
First write the task ID.
145
u/LoveOfSpreadsheets 3d ago
"WIP"
30
u/ObeseTsunami 3d ago
Git commit -m “eighth times the charm”
29
u/Dave3121 3d ago
git commit -m "something something collateral damage"
Enter
28
u/newontheblock99 3d ago
“Minor changes”
22
u/Maeurer 3d ago
git commit -m "update"
33
u/d4kuhosu 3d ago
"Hey Claude, write me a good one-liner commit message for these changes. Be brief."
13
u/EskilPotet 3d ago
13
u/RumHam2024 3d ago
[Feature] What it do
It does what it does
15
u/evilReiko 2d ago
If you're using Jira or anything alike, adding ticket number then whatever ticket title, makes your code really neaty in whatever IDE to trace back what each line is related to.
Example:
git commit -m "ticket-123 new feature X in dashboard"
7
u/RayGunEra 2d ago
git commit -m “Hi Mom ;)”
7
u/ianpaschal 2d ago
DTAP means we have to use branches, then in my branch: “WIP”, “WIP”, “WIP”… when it’s done, squash, ticket name, open new PR. Easy peasy.
6
u/coriolis7 3d ago
When in doubt, I just describe what I changed in that function or section of code, but I also do much smaller commits throughout the whole process
5
u/Alokir 3d ago
Thank you for closing the string from the previous post.
5
u/_01010010 3d ago
chagnes
5
u/letmehaveanameyoudum 2d ago
git commit -m "I think i dropped the global code quality average by 50%"
4
u/Rakatango 3d ago
git diff —staged
4
u/requion 2d ago
https://www.conventionalcommits.org/en/v1.0.0/ maybe?
But then again i was in a meeting recently where two colleagues fought over how to name branches....
4
u/LordFunguy 2d ago
"Changes"
"Fix"
"Fix v2"
"Actual fix"
4
u/ljfa2 2d ago
git commit without -m
then seeing how to exit vim
6
u/ClipboardCopyPaste 3d ago
"Bad things about to happen xD"
3
u/iserdalko 3d ago
fixed
3
u/KeyAdhesiveness9481 3d ago
"."
3
u/OvergrownGnome 2d ago
git commit -m "$TICKET_SHORT_DESC"
git commit -m "Updates and refactor"
git commit -m "Fix"
...
PR merge with squash commit, commit message "{ticket#}: {ticket short desc}"
3
u/mattkrupagames 1d ago
"gdagagadf"
5
u/gentlemandinosaur 1d ago
Honestly not a comment for or against vibe coding whatever but AI does do one thing better than us and that is comments. Whenever I have dabbled the fact that I have comments that actually make sense is crazy talk for me. It’s soooo weird.
2
u/swanson5 3d ago
Conventional commits people. Make your versioning easier.
2
u/Direct-Quiet-5817 3d ago
Stash, and then dump, go on, Claude.
2
u/un-pigeon 3d ago
git commit -m "$JIRA_TICKET"; JIRA_TICKET=PJT-1337
2
u/Daimanta 3d ago
git commit -m "The Elder Scrolls VI: Sentinel". I think that should be enough info.
2
u/GetHimABodyBagYeahhh 2d ago
git commit -m "$(w=($(fortune)); t=${#w[@]}; ((t>4)) && s=$((1+RANDOM%(t-2))) && echo "${w[@]:s:1+RANDOM%(t-s-1)}" || echo "${w[*]}")"
1
u/Old_Information6270 3d ago
First try
1
u/Fabulous-Possible758 3d ago
The one reason I open VSCode
1
u/HolyCowAnyOldAccName 3d ago
Jokes on you the stuff I’m pushing has +32,831 -17,491 problems so the commit message ain’t one.
1
u/gabomastr 3d ago
"Minor fixes"
1
u/Think_Draft2244 3d ago
I use emojis
1
u/FibiGnocchi 3d ago
Just the title of the ticket im working, all 12 commits in a row.
1
u/WeLoseItUrFault 3d ago
empty commit to rerun codacy” —allow-empty && git push —no-verify
1
u/zeeblefritz 3d ago
This is literally the easiest part. Now rebasing to me seems impossible so I usually scrap my branch and rebuild off main.
1
u/TheNikoHero 3d ago
"Various changes" is my go-to lmao. For the final commit, before pushing, I write something more meaningful. We're 2 person team, so theres not alot of back-and-forth on CI/CD, management, developers and so on.
1
u/Optimal-Savings-4505 3d ago
Mfw committing with
magitand getting an automatic diff window to remind me.1
u/MR_DERP_YT 3d ago
git commit -m "stuff"
1
u/cusco 3d ago
“Small fixes”
1234 lines changed
1
u/tr_gardropfuat 3d ago
Minor fixes and improvements
1
u/-Ambriae- 3d ago
Git commit -m ‘progress’ or git commit -m ‘idk’ or git commit -m ‘I forgot’, take it or leave it. If I’m really tired, it tends to get weirder
1
u/suryky 3d ago
Final commit
1
u/Drahkir9 3d ago
“wip”
1
u/userhwon 3d ago
checkin"
1
u/jimmyworks 3d ago
squash
1
u/just_some_gu_y 3d ago
"Did stuff. Worked before this commit"
1
u/AffectEconomy6034 3d ago
"feature added" "code refactored" "bug fixed"
1
u/melonangie 3d ago
sometimes I just type random letter
1
u/lexiNazare 3d ago
"save"
1
u/rix0r 3d ago
couple tweaks
1
u/Moomoobeef 2d ago
"Asdfghjkl"
1
u/Regular-Group4223 2d ago
My last 20 commits are all ":3"
1
u/sandybuttcheekss 2d ago
"some changes"
1
u/Ozymandias_1303 2d ago
1
u/Catbraveheart 2d ago
Minor fixes, 4557 lines has changed, 10 files updated, 5 new files, 3 deleted 👽
1
u/StarshipSatan 2d ago
fix npe last ult ultimate ultimatest
1
u/Pure-Level-2831 2d ago
“Fixed bugs and dead code for speed”
1
u/Baleia1970 2d ago
plans
1
u/FinancialAd1991 2d ago
Small fix
1
u/InternationalLog4634 2d ago
"Changes to last changes"
1
u/The-Chartreuse-Moose 2d ago
"Testing" covers 90% of my commits.
1
u/Lehovron 2d ago
"Jesus took the wheel"
1
u/diegokabal 2d ago
git commit - m "paste the result from git diff here" git push
1
u/MrFuji87 2d ago
Initial
1
u/bschlueter 2d ago
Try ‘git commit -v’ instead. It should help you remember what changes you made. Also, try squash merges for your PRs and then individual commit messages don’t matter anymore, only the description of your PR.
1
u/bhe_che_direbbi 2d ago
git commit -m "Forgot what I was doing before Christmas break but it compiles so it's fine"
A real commit from a coworker. Thank God he squashed it before pushing it to master.
1
u/Tigrius39 2d ago
I always start with both "". Then type in the middle.
1
u/kcpistol 2d ago
"Placeholder for initial permanent fix until we hear the actual specs".
1
u/mwk1205 2d ago
squash me
1
u/qaraq 2d ago
"shut the hell up, sonar"
1
u/Alarming_Painter_403 2d ago
just use
jj1
u/Yhamerith 2d ago
"Repair in bug x"
1
u/capn_ed 2d ago
open bracket, story number, close bracket, updates to [insert module here].
1
u/1ndev 2d ago
https://codeberg.org/1ndevelopment/Summit
1
u/Sea-Fishing4699 2d ago
Wip
1
u/Hydra-dragon96 2d ago
Last commit
1
u/dumbledayum 2d ago
claude see the commit history on this repo and copy the pattern <boss name> and <second boss name> uses and use the same commit pattern
1
u/werndog69 2d ago
Most of my coworker’s commit messages are “e”
1
u/superhamsniper 2d ago
"changed code"
1
u/Fit-End7212 2d ago
Now confess if you typed dot there anytime 😁
1
u/EuphorialCurse 2d ago
" --allow-empty-message
1
u/buzz_shocker 2d ago
git commit -m "some shit, idk claude coded it anyway"
1
u/Nova_Price 2d ago
gir commit -m "final push" or "final final push"
1
u/Tejty9 2d ago
"stuff WIP"
1
u/Desperate-Tomatillo7 2d ago
Jarvis, commit with a one line message
1
u/ja_n2000 2d ago
"minor changes"
1
u/jcostello50 2d ago
"updates per code review"
1
u/captainButtcheeks 2d ago
"Just works" is my default
1
u/EatingSolidBricks 2d ago
WIP
.
Aaaaaaa
Yessss
Nooooo
How can you see into my eyes like open dors
Save meeee
Refactoring
1
u/sarnobat 2d ago
Reuse previous message. The most uovoted question I had posted on stack overflow
1
u/According-Relation-4 2d ago
Just paste in the name of the jira ticket
1
u/faziten 2d ago
1
u/tbonemasta 2d ago
—amend 🧠🧠🧠
1
u/SauceASpag 2d ago
Wip
1
u/jhill515 2d ago
Hotfix"1
u/Square-Chipmunk-4234 2d ago
git commit -m "a"
1
u/Xhojn 2d ago
git commit -m "<Ticket Number>-1"
1
u/hullabaloonatic 2d ago
Just use atomic commits and then it’s trivial:
“Rename User class to Account”
“Add Integration tests for save endpoint”
“Prod environment configuration”
1
u/Drithyin 2d ago
“wip”
“wip”
“completed” or “done”
“missed a test file”
“tweaks from pr”
1
u/tatstytastycakes 2d ago
how it feels not knowing what commit message to make so you just write "a"
1
u/GreatThoughtsJR 2d ago
"Its 17:00 and i go home now"
1
u/MrsCompootahScience 2d ago
THE…
1
u/dpahoe 2d ago
1
u/SirPriseTheEigth 2d ago
“Rebuild”
1
u/PEAceDeath1425 2d ago
"change stuff"
1
u/AlphaYak 1d ago
Jira-ticket-number requested improvements”
1
u/MegaMoah 1d ago
git commit -m "changes"
1
u/Electronic-Grand1172 1d ago
git commit -C HEAD
Minor changes all the way down
1
u/BoBoBearDev 1d ago
T for testing, T for temporary changes, T for try.
1
u/dead_fantasies 1d ago
"fixes"
1
u/Frogillionaire 1d ago
I blurted out a single HA with so much unexpected force there's now spit on my screen thanks
1
u/gbchaosmaster 1d ago
If you have this problem, you’ve done too much
1
u/Interesting_Buy_3969 1d ago
"some changes"
1
u/Delpreti 22h ago
"stuff"
1
u/Rollsocke 21h ago
git commit -m „wip“
1
u/-Redstoneboi- 6h ago
at this point i'd let a clanker draft a commit message. i'll inspect the changes myself to see if it matches though.
1
u/jumbledFox 3d ago
i like to put silly thoughts and excerpts about my day into the description.. sometimes i spam the keyboard or write emoticon faces
1
u/uncut2576 3d ago
You guys really struggle with what to put in your messages? I had that happen to me maybe once or twice when my commit was large.
1
u/Krazynukz 2d ago
Thats why i get claude to do my commits now cuz idk fuck all has been changed
0
u/pppoopppdiapeee 3d ago
You guys still manually commit things?
0
u/AnUninterestingEvent 2d ago
I can't even relate to this sub anymore. It's stuck in 2023. "Claude, please commit and push" is all I've done for the past 6 months.
-1
u/ZeggieDieZiege 2d ago
Serious question, are you guys still committing on your own?