First instance where a new branch is required
Navigate to the Repos > Branches
Dropdown and select the relevant report repository
Click on the three dots to open a menu and select “New Branch”
- Select the three dots beside Develop to create a Test branch
- Select the three dots beside Test to create a Production branch
Name the branch "release", ensure it is based on the item you selected in the form, and click “Create”
Congratulations, your report has now been transitioned into a branch for release.
After this initial transition, you will then need to use the Pull Requests in order to transition any further updates into the other phases.
Also, from this point, you can now set up the release pipeline process so that your files will automatically publish to the report workspace.
Target Branch already exists – Create a Pull Request
When the target branch already exists for your repository, you will need to create a Pull Request in order to transition updates into another phase.
Navigate to Repos > Pull requests
Dropdown and select the relevant report repository
Click on “New pull request”
Select the "develop" into "release" pull request configuration
Enter the details of the transition, an example is given below:
- Title: Version 0.3.3 - dd mmm yyyy
- Description: Change Log Description
Please Note
The reviewers must have at least Basic or Visual Studio Licensing. Stakeholder licensed users are unable to access this screen so should not be set up as reviewers.
Click “Create”
Click “Approve” to approve your portion of the request.
All approvals completed
When all approvals have been completed, you will be able to complete the request, click “Complete”
Ensure that “Complete associated work items after merging” is not ticked
Click “Complete merge"
Your merge will process and complete, and if the release pipeline has been configured correctly, the report file will automatically begin to publish