794
"Fix"
With 400 lines changed over 50 files
"updates"
“feat: stuff”
Guilty of this one myself.
I had a commit recently that was like 2000 lines changed over 6 files. Really should have been a smaller issue.
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.
See jira-blah: is my go-to. Sometimes there's even a jira at that location/number 🤔
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 50 total commits, all of which include apologies for not doing more smaller commits
There's a bigger issue than your commit message if you don't even know what you just coded and are committing.
You see, sometimes I code something, go to bed before finishing it, come back, decide not to commit because then I'd have to think of a commit message and I just want to code, start working on an unrelated feature, do that for a couple days, get distracted by life stuff and put the project down for a few weeks/months, rinse and repeat, and then I finally get around to writing a commit message because I'm about to start a huge change and I want a restore point and I'm like. Okay, it's been like 3 months since my last commit, I'm pretty sure my code can now do something it couldn't 3 months ago but come on, I can't even remember what I had for lunch last Thursday
I'm well aware this is terrible practice but I don't know how to stop doing it
Commit more often. Maybe work in a different feature branch, and don’t be afraid to commit your half-working crappy code. If it’s a personal project/fork, it’s totally acceptable to commit often with bad commit names and small unfinished changes: you can always amend/squash the commits later. That’s how I tend to work: create a new branch, work on the feature, rebase and merge (fast forward, no merge commit). Also, maybe don’t jump around working on random features :P
Jumping around to random features is how my ADHD brain works most efficiently.
Good news, TDD is methylphenidate of software development!
but...but new feature shiny
Fr tho this is all excellent advice
load more comments
(2 replies)
load more comments
(1 replies)
^psst,^ ^git^ ^add^ ^-p^
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 https://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 👍
load more comments
(2 replies)
git commit -m “changed somethings “
git push origin master
You forgot this --force flag.
load more comments
(11 replies)
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 🤦♂️
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.
P1000x this.
I can read a diff.
I need to know why.
No, a code comment isn't good enough, it's out of date after the next commit.
load more comments
(3 replies)
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.
load more comments
(4 replies)
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] (https://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
view more: next ›
this post was submitted on 12 Dec 2023
794 points (100.0% liked)
Programmer Humor
24685 readers
381 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS