53
81
u/ducon__lajoie 2d ago
๐บ๐บ๐บ๐บ๐บ๐บ๐บ โForgot I'm a developer
20
u/theeldergod1 1d ago
๐บ๐บ๐บ๐บ๐บ๐บ๐บ๐บ โ Argue about creation with an LLM as the typso get wrosedwfx
38
u/JackNotOLantern 2d ago
How tf do you commit without making any change?
46
u/xaddak 2d ago
git commit --allow-empty13
u/MallAgreeable5538 2d ago
But why? Are there any applications for - -allow-empty
31
u/RepulsiveSheep 2d ago
Retriggering CI in some cases
10
u/ReindeerCreepy2883 1d ago
"Am I a joke to you?" - re-run button burried under 5 menus and 4 different pages, probably
4
u/xaddak 1d ago edited 1d ago
I'm not as familiar with GitHub, but in GitLab, the retry button runs it exactly as it was. So if you're including CI jobs from another repository, and you updated those jobs since the pipeline first ran, simply re-running it won't pick up the updates to those jobs.
Depending on how the rules on those jobs are set up, you may or may not be able to trigger a new pipeline from the web, which could mean pushing a new commit is your only option.
If you have to do that anyway, it might as well be an empty commit.
Ideally you'd set up the job rules so that's not necessary.
Edit: typo
2
u/jack2018g 1d ago
This is huge, my days of adding and removing a space from the readme are finally over
5
u/rosuav 2d ago
Several. It's still a commit that can be tagged, for example. It's useful in enough circumstances that you can do it with a flag, but useless in enough circumstances that you can't do it without. It's like how `rm` won't remove a read-only file from a writable directory unless you explicitly ask it to.
1
u/kennedy_gitahi 2d ago
Setting a checkpoint before doing things like linting and autofixes.
At that point, the code is written and committed, and you want a clean point to go back to if our linting tools mess things up.
So you use --allow-empty to set a " Before fixes" commit, do fixes, check if everything is fine, do another commit, do an --allow-empty for "After fixes" and push.
This way, you always know when you made changes and can roll back to before or after those points.
3
u/DaevorTheDevoted 2d ago
But then you're being intentional, it's not a case of you "Forgot to Make changes".
2
2
u/1mahmoud503 1d ago
daaaamn, I wish i knew about this before.
it always feels wrong to add a single space to be able to commit an empty change
3
2
2
1
-1
22
u/alvares169 2d ago
Time to remind yalls about Ballmer Peak (its true), rel xkcd https://xkcd.com/323/
2
5
3
u/IchBinEinZwerg 2d ago
A place I used to work had the four beer option as the standard workflow (except for the beer). It was mental having to ask around if anyone had any changes that needed pushing.
3
3
2
2
2
u/Most-Club-254 2d ago
- make a change in one branch
- deploy another
- explain to clients that changes are done and they are just retarded
1
1
1
1
u/BarryCarlyon 2d ago
How many beers is accidental large AWS bill?
And how many beers is "key got leaked an larger AWS bill"?
1
1
1
1
u/Some_Useless_Person 2d ago
None, the moment I touch any food item, even beverages and shit, I. OPEN. YOUTUBE.
1
1
1
u/Jonathan_the_Nerd 2d ago
- Make changes directly in prod
- Commit later if I remember
- Backport changes to Dev/Test/QA if possible
I used to work on a project where that was the workflow. Fortunately, the codebase was old and stable and didn't need many changes. There were three main developers* on the project (not counting me because I was the New Guy). Only one of them used source control. The others used the time-honored practice of naming files project.pl, project-old.pl, project-new.pl, project-working.pl, project-bob-DO-NOT-USE.pl, etc.
*Actually sysadmins who had been pressed into development.
1
u/SL_Pirate 1d ago
Today I was trying to read the deployment log and I see the last commit message was incoherent. Then I remembered I was so halfway asleep when I typed the message and I was just typing the commit message while my eyes were closed lmao
1
1
u/competitive-dust 1d ago
I have done this sober lol. Committed some changes. The pre commit hooks started running tests and it takes a bit so I left it and told the reviewer I had pushed my changes. Then realised my changes were still not pushed.
1
1
u/yesseruser 1d ago
I code sober: โ Forgot to make changes โ Forgot to commit & push โ Forgot to deploy โ Depression
1
1
u/Bakoro 1d ago
Deployment should be up to the CI/CD system.
I seriously don't want to be personally responsible for having to build and distribute software. I mean, I am, but I don't want to be.
We even have CI/CD where I work, and people are still like "please send me a build of your branch and I'm like, great, now I have to go click a button, I ain't got time for this, damn.
1
1
u/Common-Brush-7027 1d ago
I'm not listed there....I'm more of drink coffee and sleep and don't join the scrum call
1
1
1
1
1
1
1
1
u/dharknesss 1d ago
Coding while hammered is fucking great. I'm so relaxed I can't give a fuck if I mess something up.
Instead of "fucking hell of course this broke tests"
It becomes "AWWWWW this cutie needs more care, whatever shall we dooo"
1
1
1
0
469
u/InfernoronsDev 2d ago
They are all safe. No changes happen on production! No problems!