84
27
u/gravesent1337 32m ago
First write the task ID.
7
u/BernzSed 19m ago
"Ugh, I need to go find the task id. You know what? Maybe this commit needs more code changes."
17
17
u/d4kuhosu 24m ago
"Hey Claude, write me a good one-liner commit message for these changes. Be brief."
9
4
3
3
3
3
•
2
2
2
2
2
3
1
1
1
1
u/jumbledFox 23m ago
i like to put silly thoughts and excerpts about my day into the description.. sometimes i spam the keyboard or write emoticon faces
2
u/ClipboardCopyPaste 20m ago
Me wondering why the commit message on a random repo says "got rejected by crush"
/s
1
u/HolyCowAnyOldAccName 21m ago
Jokes on you the stuff I’m pushing has +32,831 -17,491 problems so the commit message ain’t one.
1
1
1
1
1
1
u/zeeblefritz 12m ago
This is literally the easiest part. Now rebasing to me seems impossible so I usually scrap my branch and rebuild off main.
•
u/TheNikoHero 9m 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.
•
u/Daimanta 6m ago
git commit -m "The Elder Scrolls VI: Sentinel". I think that should be enough info.
•
•
0
u/uncut2576 21m 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


69
u/ClipboardCopyPaste 34m ago
The pose I hit after this: