Summary

Completed

Your team wanted a way to protect the Bicep code on your main branch and prevent accidental changes that might affect your production Azure resources. You wanted to review any Bicep code before it's merged into your main branch.

In this module, you learned how to use feature branches to separate your team's in-progress work from the Bicep code that you use for your real Azure environments. You also learned how to use pull requests so that your team can review your Bicep code changes before they're merged and deployed.

You've now increased your team's confidence in your Bicep development process and reduced the chances of anyone deploying faulty Bicep code to your production environment.

References

• Branching
  • Merge strategies and squash merge
  • Trunk-based development
  • Gitflow
  • GitHub flow
  • Patterns for Managing Source Code Branches
• Pull requests on Microsoft Learn
  • Manage repository changes by using pull requests on GitHub
  • Collaborate with pull requests in Azure Repos
• Bicep best practices
  • Structure your Bicep code for collaboration
  • Best practices for Bicep