deleted by creator
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
deleted by creator
git commit -m “break codec sync if UA = firefox/gecko”
do
git commit -vand 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.
Code comments for "why"s that persist. Commits for why’s that are temporary.
If you need to run X before Y, add a comment. If you added X before why because it was easier, leave it in a commit
If you need to run X before Y…
Add a test that asserts that.
“Fix”
With 400 lines changed over 50 files
“updates”
“feat: stuff”
Guilty of this one myself.
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.
‘fixed odd or even function for values 600 to 950, plus other stuff I forgot to commit earlier’
“Bits were fiddled, possibly in the right way”
My butterfly was having a bad day so I can’t be sure, sorry
‘Change’ if I’m feeling particularly chaotic.
git commit -m $(date)
See jira-blah: is my go-to. Sometimes there’s even a jira at that location/number 🤔
deleted by creator
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”
Well such an informative reply! Thanks mate 👍
Full send.
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!
deleted by creator
“blah”
git commit -m “changed somethings “
git push origin master
Do you always have to do origin master? I’ve seen it where sometimes just git push works and other times not.
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
I just meant it not auto creating a new matching named branch.
where it Just Works, the branch is set up to track a remote branch
https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches
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?
Force push main, straight to jail🤣
Yup yup, usually you’re on a branch, sometimes a tag. I mean it’s all just pointers to references at the end of the day. I tend to treat Git like a story book, some folks still act like it’s SVN.
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.
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.Lol why not just delete the whole project from GitHub… I mean, everyone has a copy, right?😱
I tired that, still was having issues, weeeird.
uh in any actual company you almost never push to origin master. so I think it’s a joke.
Depends on the configuration right?
You can work on your branch and then push that to integration for example.
I mean you’re not working on your local master/main branch right?
In most actually companies you can try push to origin master, but it’ll likely get rejected by the repo’s security policies.
Not with that attitude! /s
Force push Fridays!
You forgot this
--forceflag.I’m too lazy, I use -f
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.
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 🤦♂️
“stuff”
“Commit”
The usual reason would be “because coworkers”
I’m using Copilot for it right now. It works on half of the cases.
That’s about 300% better than my average!
Forward three hours, me using thesaurus.com to try fit the whole gist of my change into the first line.
