To do this, get the diff between main and production branches. Compare
here.
Production deployment is automated with github actions, but you will need to
update the production branch for it to deploy changes.
Switch to the production branch, ensure it is updated from origin, then
rebase it with origin/main.
$ git fetch
$ git checkout production
$ git reset --hard origin/production
$ git rebase origin/main
$ git push --force-with-lease
NOTE: git push --force-with-lease is important, the force push will be
rejected if changes have been made in orgin that differ from your local branch.
Monitor the github actions page to check status of the automated deployment.
After a successful deployment, you will need to update the release log
here.
To get the docker image, find the latest version with the tag production on
the container registry
page.
In certain circumstances, you might see multiple images listed. In this case, you can find the correct one by looking in Azure under Home → Container Apps → prodghbs-buyforyourschool → Containers → Properties → Image and tag.
Staging is automatically deployed with changes appear in main.
Monitor the github actions page to check status of the automated deployment.
Development deployment is automated with github actions, but you will need to
update the development branch for it to deploy changes.
Switch to the development branch, ensure it is updated from origin, then
rebase it with main.
$ git fetch
$ git checkout development
$ git reset --hard origin/development
$ git rebase your-feature-branch
$ git push --force-with-lease
NOTE: git push --force-with-lease is important, the force push will be
rejected if changes have been made in orgin that differ from your local branch.
This ensures you don't overwrite other developer's changes on development.
If you need to make repeated changes, always reset development and then
rebase your feature branch again.
Monitor the github actions page to check status of the automated deployment.