- 2 years
Real talk: I have worked at a company where an exec briefly had the bright idea to rank developers on number of commits made.
You can imagine how that turned out.
He wasn’t an exec for very long.
- QuazarOmega@lemy.lolEnglish2 years
lmaoo, I can’t believe someone actually did that and was serious about it.
I’m already imagining commits piling up with comments like:- “add a newline”
- “move function up”
- “rename variable
userstouser_list” - “Revert previous commit”
- “no John, it’s
user_listand that’s it, don’t you dare change it again”
He wasn’t an exec for very long.
Good riddance I guess
- 2 years
Oh, no, we can do better.
Every single line of every single PR is an individual commit. And never squash-commit.
- 2 years
If you really want to nuke it from orbit: do it for every character.
It is absolutely technically feasible to go further than that, but I think that’s the point of diminishing returns in terms of effort.
- 2 years
Not Shall330, but double quotes can imply variables in the string in some languages.
- 2 years
I have no preference! It was to do with Spring/yaml config and some really strange conflict which required the use of single quotes. I’m still a total noob in the world of software dev, so I wouldn’t be able to explain why it worked 🤣
- 2 years
You’re going to regret not adding the second sentence to the commit message some day.
- 2 years
Bold of you to assume there is a cohesive theme to dotfile commits. Usually it’s just been long enough that I don’t want to lose my latest tweaks
- 2 years
My commit messages have gotten extremely lazy since I start squashing all my commits down to one. I just describe the PR on the first commit message and write nonsense in all the others.
- 2 years
I’ve been adding the commit shas + messages to the final description, if anyone wants to see my exploratory work.
- 2 years
I know that if you are on the local repository where the commits were originally created they’ll remain accessible through recovery methods but AFAIK orphaned commits aren’t synced to other machines.
- 2 years
That’s correct. This is for work, which uses GitHub. The dangling commits remain accessible via their sha through the web ui, so I can link them in the PR description. I don’t put them in the actual commit message.
I think these are garbage collected eventually, but no idea on cadence. It’s long, anyway.
- 2 years
Update coffee list and tex files.
…and yes we have our office coffee list in a git repo.
- 2 years
Do new hires have to submit a pull request to get in on it? If so, I’m guessing the non-technical staff don’t get to drink a lot of coffee.
- 2 years
It’s actually just a paper list where people make ticks for coffee. That is then manually synced to an hledger file in git.
- 2 years
For what? To keep track of who’s drinking coffee? Are you charging for coffee?
2 yearsDo you have any plans to open source your coffee list? I want to add this feature where I get an iced coffee in the morning
- 2 years
“Changed consent banner text to reflect from legal, even though they are wrong”
- 2 years
“circumvented GDPR despite calling out strong ethical objections, because legal & management are forcing me to”
- 2 years
“28496 - there, it’s fucking fixed you twat waffle.”
Ticketed bug bosses son found. Dude nagged his dad who nagged us until it got fixed. Boss doesn’t review code. And for the sake of a half dozen coworkers, I hope he never does.
- 2 years
“;”
Previous commit was some stupid easy fix I didn’t even bother compiling. Well, I should have, because it was the first time in recent memory I committed some code with a missing semicolon…
Before anyone asks : no, we don’t do reviews ¯\_(ツ)_/¯
- 2 years
For those I just commit with the message “ngl there’s a lot of changes in here”
- 2 years
git commit -m “if this doesn’t fix it I’m looking up availabilities at my nearest maccas”
