Tutorials Microservices with .NET
Git Branching for ASP.NET Core Development — Complete Guide
Git Branching for ASP.NET Core Development — Complete Guide: free step-by-step lesson with examples, common mistakes, and interview tips — part of Microservices with .NET on Toolliyo Academy.
On this page
Microservices with .NET · Lesson 90 of 131
Git Branching for ASP.NET Core Development
Beginner ✓ → Intermediate ✓ → Advanced → Professional
Advanced · 3 — Production skills · ~10 min · Module 10: Git and GitHub
What is this?
Branching strategy for ShopNest: main (production), develop (integration), feature/* per story, hotfix/* for urgent payment bugs.
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
- Agree on branch naming: feature/, bugfix/, hotfix/.
- Create feature branch for next lesson change.
- Push and open draft PR.
- Change a string or route in the example and save — watch Swagger or the RabbitMQ Management UI update.
- 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.