How would you structure a Git workflow for a .NET team working on APIs and frontend changes?

I would design the Git workflow around release risk and team ownership. For a product team, the main branch should represent code that can be built, tested, and promoted. Pull requests should be small enough to review properly, and risky changes like database migrations or authentication changes should receive extra attention. If the team needs release branches, I would define when they are cut, who maintains them, and how fixes flow back to main. A messy Git workflow often becomes a delivery and incident-management problem later.