3 ms·
I think it's due to people working in badly setup monorepos: - CI/CD that runs on the entire thing - merge policy that requires branch being up-to-date even f
by 0x457 4y ago
I think it's due to people working in badly setup monorepos:
- CI/CD that runs on the entire thing
- merge policy that requires branch being up-to-date even for FF merges
- I once spent an entire day trying to merge a PR because CI for other people changes was taking N minutes, but mine was N + 1 minutes. I kid you not, I resigned a week after that day because I just couldn't.
- Messy organization within the repo
- People wanted tag releases, so every single service within monorepo was on the same version and some of had months since last activity
- Whole kitchen sink in one repo: terraform, Ansible, source code, fucking debian packages, secrets (sop) whatever else VPoE thinks is part of engineering.
- include over an include in pipeline files (this was GitLab CI) that is impossible to navigate because of name collisions.
You gripes about many-repos are IMO wrong, though. If you have to duplicate things, then you're doing it wrong.