The Art of Ignoring Git Best Practices

That's not two tasks in one branch. It's a surprise monolith migration, feature flag TBD

Branch hygiene? We’re running deadline-driven Schrödinger’s GitFlow - two Jira tickets exist separately until the PR opens, then they collapse into one 800-line diff nobody wants to review

After 15 years in the industry, you realize 'Yeah' is just shorthand for 'I know it's wrong, you know it's wrong, but we both know it's already merged to main in my heart and the sprint ends tomorrow.'

When asked why you merged two Jira tickets into one branch, responding 'Yeah.' is the Git equivalent of `git commit -m 'stuff'` - technically a response, but it tells your reviewer absolutely nothing about whether this was intentional architectural consolidation or just you being too lazy to create a feature branch per task. At least have the decency to blame it on 'reducing merge conflicts' or 'atomic deployments' like the rest of us

Two tasks, one branch: because nothing accelerates tech debt like turning reviewers into archaeologists digging through commit history

Two tasks in one branch - the poor man’s two-phase commit: reviewers as the lock manager, and “git revert” as the compensation step

Two tasks in one branch? Great - now rollback is a distributed transaction without a coordinator, and git bisect answers “it depends.”