Set branch protection rules

I need branch protection applied to the main branch so regressions stop slipping in. Require pull requests, enable required reviewers set to two, and prevent force pushes and deletions. Put the protection in place today and verify it on the repository named payment-service. Confirm that the protection applies to admins and that the branch requires linear history before I give the team the go-ahead.

Before I enforce protection on main, make the rules review-friendly for the team's workflow: surface which file paths need exceptions, show how status checks and review counts will block current open PRs, and flag any active automation that will break (dependabot, release bot). Suggest the minimal relaxations that still stop direct pushes while avoiding a dozen broken PRs.

I turned on branch protection for payment-service main and required two reviewers; now four open pull requests are marked blocked and the release bot reporter failed. I am worried this will stall the Friday deployment and cause the release lead to escalate. I cannot tell whether those PRs can be remediated by re-requesting reviews, by merging with an exemption, or by adjusting the rule. What likely caused the block and what is the safest next step to restore momentum without compromising safety?

Across repositories, we oscillate between no protection and overbearing rules that stall work. We waste time unblocking trivial fixes or reworking active PRs. I want a practical habit change so protections stop being emergency toggles and become predictable controls. Recommend a daily checklist and a minimal rule set that balances developer flow with release safety for teams that ship twice a week.