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
… Isn’t master the current production code? How do you get a master that haven’t been touched in 15 years?
Because you have a terrible branching strategy
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.
I think OP is talking about the fact that most new projects use “main” now, so “master” likely indicates an older project.
When branches don’t check out… that’s a problem.
Checkout followed by 400 build errors because your entire toolchain and build pipeline has changed since you last touched it.
