Business Central is a sophisticated web tooling suite that provides a full lifecycle of business rules and process-based applications from authoring to deployment, and management to track. Business Central uses internally git, but also exposes some features of it to more advanced users.
Git became ubiquitous in software development; however, it is not always clear what’s the architecture impact to use a distributed version control system, especially embedding it in a complex web tooling stack.
This post aims to consolidate all blog posts about Business Central and Git. Please let me know in the comments if you have any suggestion for a topic not covered in this guide. Hope you enjoy the read!
Business Central Internals about NIO2 JGit FileSystem implementation
Business Central and Locks: how to avoid conflicts and users step in others toes
Built-in external integration
Branch status, and Role-based access to branches
Change Request system
Scaling and Isolating Repositories with Forks and Sync
How to use post-commit hooks to create a bi-directional integration with external git infrastructure
How to define a content based change to trigger an integration process
How to integrate Business Central to use external Pull Requests
Multiple Feature Streams
Hotfix to Production Issue
Maker-Checker (or four eyes principle) and Merging
Setup Integration with Enterprise Repository
Avoid Changes Directly into Master
Lightweight Deployment for Developers
Discourage Multiple Users From Editing Same Asset
Alert for potential outdated local copy/branch
Here also some relevant external references that covers Business Central and Git: