-
Notifications
You must be signed in to change notification settings - Fork 228
Hotfix Release Instructions
Mike Ochs edited this page Aug 17, 2022
·
2 revisions
To create a Hotfix release use the following steps.
- Create a "hotfix" branch off of the release tag of the release requiring the hotfix. If there's an existing hotfix branch it should be deleted. Replace TAG_NAME with the name of the release tag e.g. CoEStarterKit-August2022
git checkout tags/TAG_NAME -b hotfix
- Create a new branch based on the hotfix branch. Replace MY_HOTFIX_BRANCH_NAME with the name of the branch you will make your changes in.
git checkout hotfix -b MY_HOTFIX_BRANCH_NAME
- Make your changes in MY_HOTFIX_BRANCH_NAME
- Commit the changes and create a PR from MY_HOTFIX_BRANCH_NAME to Hotfix
- Creating a PR into the hotfix branch will kick off validation and automated testing similar to creating a PR into main.
- Once the PR checks complete, approve the PR and complete to merge the changes into hotfix
- Merging into the hotfix will kick off the deployment to test similar to merging into main
- Once the deployment to test has completed and the hotfix has been tested, run the deploy to production pipeline to push the test build to production.
- After the deployment to production is complete run the create-release-CoEStarterKit pipeline and select the hotfix branch and set the Hotfix Number