Search icon
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Mastering Microsoft Dynamics 365 Business Central

You're reading from  Mastering Microsoft Dynamics 365 Business Central

Product type Book
Published in Dec 2019
Publisher Packt
ISBN-13 9781789951257
Pages 770 pages
Edition 1st Edition
Languages
Authors (2):
Stefano Demiliani Stefano Demiliani
Profile icon Stefano Demiliani
Duilio Tacconi Duilio Tacconi
Profile icon Duilio Tacconi
View More author details

Table of Contents (25) Chapters

Preface Section 1: Dynamics 365 Business Central - Platform Overview and the Basics of Modern Development
Microsoft Dynamics 365 Business Central Overview Mastering a Modern Development Environment Online and Container-Based Sandboxes Section 2: Developing Extensions for Dynamics 365 Business Central
Extension Development Fundamentals Developing a Customized Solution for Dynamics 365 Business Central Advanced AL Development Report Development with AL Section 3: Debugging, Testing, and Release Management (DevOps)
Installing and Upgrading Extensions Debugging Automated Test Development with AL Source Control Management and DevOps with Business Central Section 4: Advanced Integrations with Dynamics 365 Business Central
Dynamics 365 Business Central APIs Serverless Business Processes with Business Central and Azure Monitoring, Scaling, and CI/CD with Azure Functions Business Central and Integration with the Power Platform Section 5: Moving Solutions to the New Extension Model
Integrating Machine Learning into Dynamics 365 Business Central Moving Existing ISV Solutions to the New Extension Model Useful and Proficient Tools for AL Developers Other Books You May Enjoy

Branching policies

To maintain the quality of your app, you can define policies that must be met before changes from the developer can be integrated into the selected branch.

Mostly, the policy is defined on the master branch, but it could be any branch you want to keep healthy. If you define the policy for a branch, changes cannot be pushed into this branch directly, but only through Pull Requests (PRs). See the Pull request section for more details. In this way, each change is checked and tested, and if the policy is not met, the change will not make it into the branch. You can define the following in the policy:

  • The minimum number of reviewers: This is how many reviewers must approve the PR to be accepted.
  • Check for linked work items: This forces developers to associate the PR with work items to have links between requirements and changes.
  • Check for comment resolution...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}