MSDyn365FO development process for a PBI or bug when using Git

In one of my previous posts I´ve described how to translate your TFVC flow to Git flow during development of MSDyn365FO. In this post I want to show you the development process for a PBI or bug when using Git in combination with Microsoft Dynamics 365 for Finance and Operation.

The starting point for the development process is, that you have a product backlog item (PBI) or a bug logged in e. g. Azure DevOps. The next step is to login to your development VM and start the process described as following.

1. Checkout development branch and pull latest version

First you should checkout your development branch e. g. develop and pull the latest version from the remote repository to your local repository.

2. Create new branch and checkout the created branch

To start your development, you have to create a new branch based on the development branch. After the creation of the new branch you have to checkout this branch to point your working directory to this branch.

3. Do your changes

Now it´s time to do your changes. You can “simply” work as usual with Visual Studio to change, add or delete MSDyn365FO elements.

4. Stage changes

After you did your changes you have to stage your changes. The list of staged changes will include changed, added or deleted MSDyn365FO elements.

5. Commit and push changes

To get your changes under version control you have to commit the changes to your local repository. To transfer the commit to the server side remote repository you should perform a push of the changes.

6. Create pull request incl. assign PBI/bug and Reviewers

When you´re done with your changes you should create a pull request for your committed and pushed changes, assign the PBI/bug to which the changes are related and assign Reviewers.

7. Optional: Commit and push changes related to pull request

When you got feedback via the pull request to changes something, you can do those changes and commit/push additional changes for your pull request.

8. Complete pull request

After your pull request got approved and the related build was successful, you can complete the pull request which merges and commits the changes to the target branch.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s