Submitted 11 months ago by hypnotic_nerd@programming.dev to programmer_humor@programming.dev
https://programming.dev/pictrs/image/f5b1c1d0-8942-4b36-92f2-fc0b05a94098.jpeg
Every time I commit I have to look through git diff, figure out what the hell I actually did, come up with something intelligent to say about jt, possibly split the commit into multiple commits if I changed multiple things, do some shuffling with git reset and git add…
For some reason all my personal projects are all like 4K SLoC with 20 total commits, all of which include apologies for not doing more smaller commits
I spend much time splitting them up inside visual studio by file and individual lines changed to try and separate my many simultaneous changes into several somewhat usable commits. If I was stupid enough to make some big refactor at the same time I might just have to throw in the towel… It’s really painful after a few weeks to try and pick up the pieces of what I was doing but never commited too lol.
Just use What The Commit.
You can also create a git alias:
git config --global alias.yolo ‘!git add -A && git commit -m “$(curl --silent --fail whatthecommit.com/index.txt)”’
Now you can just type ‘git yolo’ to create a commit!
“Make Sure You Are Square With Your God Before Trying To Merge This”
Full send.
Well such an informative reply! Thanks mate 👍
Thanks for that, I’ve been laughing like a little kid:
“hoo boy” “lol” “Become a programmer, they said. It’ll be fun, they said.”
I can feel those so well! :')
“Chuck Norris Emailed Me This Patch… I’m Not Going To Question It”
My first script ever was written in lua for a world of warcraft macro to spit out chuck norris one liners. People in the barrens hated me.
Well that’s about half my commit messages that are going to be nonsense on weekends projects, now. Thank you!
Psst,
git add -p
What does this?
Better yet git commit -p
uuuuuuuu. and you could do -m to describe the commit.
next they’ll add --push/-P.
perhaps add -r for fetch/rebase then commit.
one command to rule them all! 😈
git commit -m “changed somethings “ git push origin master
You forgot this –force flag.
I’m too lazy, I use -f
Do you always have to do origin master? I’ve seen it where sometimes just git push works and other times not.
uh in any actual company you almost never push to origin master. so I think it’s a joke.
I was being more evil than that, saying that if one is gonna push direct to main, might as well maximize the possible damage to everyone else’s branch.
where it Just Works, the branch is set up to track a remote branch
That’s part of the joke, I think. If it’s a repo more than just you use, you would almost never push directly to the main branch.
push origin your/branch
Pushes, you guessed it, your/branch!
Head is usually your checked out working branch if you’re not in a headless state, right?
I think it depends what branch your local version of the repo is set to. If you’re already in master then it’ll push there, if you’re in a testing branch then you can push it straight to master instead by telling it to
The usual reason would be “because coworkers”
do git commit -v and then just summarize the diff you have in your editor in a human readable form.
Don’t just summarize the content though, summarize the rationale or how things connect. I can read your diff myself to see what changed, I want to know the logical connections, the reason you did X and not Y, etc.
Or just say “stuff” and provide that context in the PR description separately, no need to overdo the commit log on a feature branch if you’re using squash merges from your PR.
1000x this.
I can read a diff.
I need to know why.
No, a code comment isn’t good enough, it’s out the f date after the next commit.
I’m using Copilot for it right now. It works on half of the cases.
That’s about 300% better than my average!
For me, it was my boss gave me a programming task which he knew would take hours or a day or two… and then 15 minutes later tells me to “switch focus” and do a menial task that any of my five coworkers could do 🤦♂️
That’s in any bloody workplace! Especially if there is o synergy between different teams.
Forward three hours, me using thesaurus.com to try fit the whole gist of my change into the first line.
Oh god I feel so called out. I wish I paid more attention to my commit messages but I’m usually too busy fixing the directory structure and refactoring. Sigh.
My company collapses into a single commit at merge so idgaf what the commit message is anymore. Though I would prefer not collapsing them.
Master should just have the feature description commits, not the hundred commits it took to get there after refactoring the code for the 3rd time and pulling changes from master since it’s taken so long to get done.
I prefer that approach. We work with smaller tasks, so it makea more sense, plus it helps keep the master clean and if you want a more detailed view of the specific commits, you just have to click on the link to the PR. It’s a better way to organise it IMO
Yeah I worked at a place like that, but it made sense because we were also expected to keep PRs small, so a good commit message for several squashed ones was perfectly fine.
Me when I have done too many tasks for one commit, but someone once told me you should never have the word “and” in your commit message.
git commit -m “directory_x:file_i.so: did x and y; directory_x:file_ii.so: fixed z”
You should not use -m, you should write commit body!
Why? My coworkers are barely literate and won’t read anything with more than 4 or 5 words, writing a commit body would be a waste of time.
Nah, most commits don’t need a body
[conventional commits] (www.conventionalcommits.org/en/v1.0.0/) will save you.
or maybe commitizen if you’d like not to write them by hand.
and maybe commit and tag version, which will create changelogs for you of you follow semver
reminds me of what youtube was doing to firefox users for awhile.
git commit -m “break codec sync if UA = firefox/gecko”
“blah”
Maiznieks@lemmy.world 11 months ago
“Fix”
obrenden@lemmy.world 11 months ago
With 400 lines changed over 50 files
hypnotic_nerd@programming.dev 11 months ago
“updates”
Jeremyward@lemmy.world 11 months ago
I had a commit recently that was like 2000 lines changed over 6 files. Really should have been a smaller issue.
Dkarma@lemmy.world 11 months ago
Y tho??? Holy shit. Commits should be like functions. One thing and one thing only. Maybe a small group of files like the same change over multiple config files. 50 is insane to me.
frezik@midwest.social 11 months ago
“Bits were fiddled, possibly in the right way”
PixxlMan@lemmy.world 11 months ago
My butterfly was having a bad day so I can’t be sure, sorry
Dasnap@lemmy.world 11 months ago
‘Change’ if I’m feeling particularly chaotic.
ShittyKopper@lemmy.blahaj.zone 11 months ago
git commit -m $(date)
Dkarma@lemmy.world 11 months ago
See jira-blah: is my go-to. Sometimes there’s even a jira at that location/number 🤔
Meowoem@sh.itjust.works 11 months ago
‘fixed prime number function for values 600 to 950, plus other stuff I forgot to commit earlier’