It takes a mature and disciplined team to use TBD and these teams are few and far between. Every developer you add to your team (or department) increases the ri

It takes a mature and disciplined team to use TBD and these teams are few and far between. Every developer you add to your team (or department) increases the risk that someone is going to miss a test, or an edge case and ultimately break the build and blocks everyone. For me short lived branches that get merged into main dependant on passing tests and maybe a PR is by far the easiest, most reliable, and most common approach. For many of the reasons listed, I do use TBD for my side projects. Push it to main, tested, built and deployed. Easy. :)