Dataverse Git integration (Preview) - How solution components are saved
This is the last article (for now) of the series about Dataverse Git integration native capability. We have already seen: How to set up the integration between Dataverse and an Azure DevOps Git repository How to properly manage the commit+push and pull operations, and resolve conflicts What kind of ALM approach arises from the bottom up analysis of the capabilities provided by the feature Now we'll deep dive on how solution components are actually saved in the repository, and compare the solution folder structure with the one generated by PAC CLI.

This is the last article (for now) of the series about Dataverse Git integration native capability. We have already seen:
- How to set up the integration between Dataverse and an Azure DevOps Git repository
- How to properly manage the commit+push and pull operations, and resolve conflicts
- What kind of ALM approach arises from the bottom up analysis of the capabilities provided by the feature
Now we'll deep dive on how solution components are actually saved in the repository, and compare the solution folder structure with the one generated by PAC CLI.