-
Notifications
You must be signed in to change notification settings - Fork 177
HotFix Process
gomes edited this page Apr 2, 2024
·
2 revisions
Hot Fixes should be made against main to avoid having to release code that is in develop and may not be have gone through the full release process.
The process to author and deploy a hotfix is similar to the regular release process, with the only difference being it's authored based on your local changes, not the state of upstream develop.
- branch off of main (i.e
git checkout main && git fetch origin && git reset --hard origin/main && git checkout -B your_hotfix_branch
- fix your issue on your hotfix branch and commit the changes
- run
yarn release
, selectHotfix
and follow the instructions of the prompt to author a hotfix PR - depending on the approval state of the hotfix PR (at the engineer's own discretion depending on the nature of the hotfix i.e with/out approvals), run
yarn release
again to land the changes in prod