c/programmerhumor · by TechSquidTV@lemmy.world · 239dWhen you have to checkout the master branch 152 points · 7 comments · view on lemmy.world
7 Comments
eldavi@lemmy.ml · 13 pts · 239d
i was told to change the name of master recently because it carries with it the negative connotation of slavery. ie master/slave
master hasn't been updated in almost 15 years and there's no way in hell i'm going to touch that. lol
ReginaPhalange@lemmy.world · 3 pts · 238d
... Isn't master the current production code? How do you get a master that haven't been touched in 15 years?
Blaiz0r@lemmy.ml · 6 pts · 238d
Because you have a terrible branching strategy
jbloggs777@discuss.tchncs.de · 3 pts · 238d
73 feature branches in active development (most for several months), and one intern (currently on m/paternity leave) responsible for merging them. Check! In the meantime, several branches deployed to prod behind a reverse proxy with feature flags.
lengau@midwest.social · 4 pts · 238d
I think OP is talking about the fact that most new projects use "main" now, so "master" likely indicates an older project.
xia@lemmy.sdf.org · 2 pts · 238d
When branches don't check out... that's a problem.
pHr34kY@lemmy.world · 2 pts · 238d
Checkout followed by 400 build errors because your entire toolchain and build pipeline has changed since you last touched it.