> you need to be the one that monitors and accepts all pull requests I disagree at least in part. On my team all of the engineers have the ability (and respons

> you need to be the one that monitors and accepts all pull requests I disagree at least in part. On my team all of the engineers have the ability (and responsibility) to merge PRs. It empowers them and gives them a feeling of ownership. I let the experts in the affected area decide when code goes in/gets deployed as they're able to manage that better than I ever could. That being said, when something breaks, it's still the tech lead's problem, even if he/she didn't hit the merge button.