You must log in or # to comment.
This summer - GIT OUT
rm -rf * git add -A git commit -m "oops." rm -rf .git git init git add . git commit -m "bye." git push origin main --forcerm-ing.gitisn’t gonna work cuz you’ll have to re-add the remotes.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
Or just
git push origin --force blank:main
I’m not sure about the git history wipe, I can’t test it myself right now
Just test it on production, you could do it right now
I thought this was programmer humor, not programmer horror
Unironically I think this is my only shot at getting past our code debt.
Sweet ninjesus, i’m having a heart attack just imagining it
My question would be for what time zone? That seems like an important detail
Well my pull request simplified all time zones to just UTC +8:45 so we never have to worry about it again
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?
Merging all the feature branches in time is easy.
Having the project compile afterwards is hard.
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.
I am ramping a vehicle onto its roof in celebration
DO DODO DO DOO DOO. DO DODO DO DO
You are amazing, you beautiful lemmy stranger, you.
Is there a robust test suite?
Merge, test, merge, test, patch, merge, test
The test suite takes 24 hours to run fully.
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.
Every repo I can suddenly has a requirement for my $1k/license addon and won’t run without it.
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.
