Why should you care?

Order team and Payment team ship on different schedules — branches prevent half-finished Payment code from blocking Order release.

See it live — copy this example

Create a Web API project (dotnet new webapi), paste the code, then run dotnet run.

git checkout -b feature/user-registration
# work on User.Api
git push -u origin feature/user-registration
# open Pull Request on GitHub

Run Example »

This lesson uses terminal or setup steps. Run commands on your computer — the live editor appears on coding lessons.

What happened?

• GitFlow or trunk-based are common — pick one per team.
• Feature branches get PR review before merge to develop.

Try it yourself

1. Agree on branch naming: feature/, bugfix/, hotfix/.
2. Create feature branch for next lesson change.
3. Push and open draft PR.
4. Change a string or route in the example and save — watch Swagger or the RabbitMQ Management UI update.
5. Break the code on purpose (remove a semicolon), read the error message, then fix it.

Remember

Branch per feature. PR before merge. Protect main branch.