Understanding the end-to-end flow

When we create a Git repository, it gets created with a collaboration or main branch. You commit all your reviewed or approved code items in this branch. Next, whenever a developer or team is going to work on a new feature or release, you create a feature or working branch by using the main branch as the source. The team works in this feature branch during development, and once they have completed their work, they create a pull request to request merging changes from the feature branch to the main branch. This typically goes through review, and when it gets approved, these changes are merged into the main branch, as shown in Figure 10.1. This flow represents the CI part of the DevOps process. Based on the approach an organization has taken, this process repeats for a single feature or a single release with multiple features:

Figure 10.1 – End-to-end DevOps for Microsoft Fabric

For the CD part of the DevOps process...