Due to management decision, a code freeze has been mandated to the main branch. 50 feature branches have accumulated waiting to be merged.
Management has now finally approved to lift the code freeze - but only for 24 hours. Will the poor engineering team manage to merge all feature branches in time?
So maybe instead, we can clear all local + remote branches and tags, create a blank branch, delete main, rename the blank branch to main, then delete .git
Although the OP says that we can merge anything, and we might not have access to mess with branches
So every sane dev will just sit that day out, do nothing and then once it has all blown over one of them will hard reset main to right before the silly time started. Sounds like a chill time, but not a good plot for a movie imo.
So the equivalente to not wanting to make part of it and staying at home is setting repositories private a few hours before and only reopening the day after?
43 Comments
aeronmelon@lemmy.world · 176 pts · 138d
This summer - GIT OUT
forrgott@lemmy.zip · 41 pts · 138d
Oh God damn you. Have your upvote and... you know the rest...
(ノಠ益ಠ)ノ彡┻━┻
KairuByte@lemmy.dbzer0.com · 25 pts · 138d
┬──┬◡ノ(° -°ノ)
sukhmel@programming.dev · 9 pts · 138d
I expected ‘git gud’
0_o7@lemmy.dbzer0.com · 8 pts · 138d
GIT GUD & GIT OUT.
eodur@piefed.social · 105 pts · 138d
I thought this was programmer humor, not programmer horror
red_tomato@lemmy.world · 94 pts · 138d
Another movie pitch:
Due to management decision, a code freeze has been mandated to the main branch. 50 feature branches have accumulated waiting to be merged.
Management has now finally approved to lift the code freeze - but only for 24 hours. Will the poor engineering team manage to merge all feature branches in time?
Jesus_666@lemmy.world · 47 pts · 138d
Here's one for a TV show.
In 2022, a crack quality assurance team was made redundant by a CTO for a botched product launch they didn't commit.
These men promptly escaped from a maximally unstable job market to the LinkedIn underground.
Today, still wanted by recruiters, they survive as soldiers of fortune.
If you have a broken codebase, if no one else can help, and if you can find them, maybe you can hire the QA-team.
kboy101222@sh.itjust.works · 11 pts · 138d
DO DODO DO DOO DOO. DO DODO DO DO
marlowe221@lemmy.world · 9 pts · 138d
You are amazing, you beautiful lemmy stranger, you.
ArtVandelay@lemmy.world · 8 pts · 138d
I am ramping a vehicle onto its roof in celebration
otter@lemmy.ca · 17 pts · 138d
Is there a robust test suite?
Merge, test, merge, test, patch, merge, test
red_tomato@lemmy.world · 21 pts · 138d
Only some of the new code does. Unfortunately, most of the code base is 10 years old written in the good ol’ Anarchy Driven Programming paradigm.
harambe69@lemmy.dbzer0.com · 12 pts · 138d
The test suite takes 24 hours to run fully.
Miaou@jlai.lu · 5 pts · 138d
If by test you mean wait for customers to yell at us, it's super robust
grue@lemmy.world · 14 pts · 138d
Merging all the feature branches in time is easy.
Having the project compile afterwards is hard.
ugo@feddit.it · 9 pts · 138d
BeardedGingerWonder@feddit.uk · 5 pts · 138d
Merge/test/fix on a separate branch and then merge this into main when the freeze lifts?
otter@lemmy.ca · 44 pts · 138d
black_flag@lemmy.dbzer0.com · 49 pts · 138d
rm-ing.gitisn't gonna work cuz you'll have to re-add the remotes.otter@lemmy.ca · 10 pts · 138d
Oh good point 🤦
So maybe instead, we can clear all local + remote branches and tags, create a blank branch, delete main, rename the blank branch to main, then delete .git
Although the OP says that we can merge anything, and we might not have access to mess with branches
ozymandias117@lemmy.world · 12 pts · 138d
Or just
git push origin --force blank:mainfartographer@lemmy.world · 2 pts · 138d
Live your best life.
git pullblindly.otter@lemmy.ca · 11 pts · 138d
I'm not sure about the git history wipe, I can't test it myself right now
ZoteTheMighty@lemmy.zip · 32 pts · 138d
Unironically I think this is my only shot at getting past our code debt.
Rooster326@programming.dev · 8 pts · 138d
It didn't say anything about wiping previous debt
Miaou@jlai.lu · 4 pts · 138d
Wdym you don't like waiting 3 weeks for a code owner to approve a 1 line change?
ZoteTheMighty@lemmy.zip · 1 pts · 138d
"Just an FYI, you can add multiple people to code owners"
- Me, every week to that one guy
sbeak@sopuli.xyz · 16 pts · 138d
My question would be for what time zone? That seems like an important detail
VoteNixon2016@lemmy.blahaj.zone · 29 pts · 138d
Well my pull request simplified all time zones to just UTC +8:45 so we never have to worry about it again
NotAnonymousAtAll@feddit.org · 10 pts · 138d
So every sane dev will just sit that day out, do nothing and then once it has all blown over one of them will hard reset main to right before the silly time started. Sounds like a chill time, but not a good plot for a movie imo.
zalgotext@sh.itjust.works · 4 pts · 138d
IDK, that sounds like a fun twist to me
ICastFist@programming.dev · 10 pts · 138d
Sweet ninjesus, i'm having a heart attack just imagining it
nie@piefed.social · 7 pts · 138d
So the equivalente to not wanting to make part of it and staying at home is setting repositories private a few hours before and only reopening the day after?
Inucune@lemmy.world · 7 pts · 138d
Every repo I can suddenly has a requirement for my $1k/license addon and won't run without it.
gwl@lemmy.blahaj.zone · 6 pts · 138d
https://www.openchaos.dev/#votes is kinda similar to, but weekly instead (voted for submissions that automatically get merged)
fubarx@lemmy.world · 3 pts · 138d
This feels like it needs a 'Hunger Games' add-on.
InFerNo@lemmy.ml · 3 pts · 138d
What does "all tech debt is legal" mean?
sukhmel@programming.dev · 5 pts · 138d
That accumulation of a hundred years of tech debt during that 12h window is acceptable
xylogx@lemmy.world · 7 pts · 138d
Good opportunity to introduce a Cobol subsystem.
nocteb@feddit.org · 2 pts · 135d
I'd rather morge continvously
Shaker_dev@programming.dev · 2 pts · 138d
I'm not understand , what it's mean
dbx12@programming.dev · 18 pts · 138d
Shaker_dev@programming.dev · 3 pts · 138d
Thanks
SleeplessCityLights@programming.dev · 1 pts · 136d
I am taking the network down at the office on this day. I have accidentally done it before and now I know how to do it again.