You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Automating the creation of pull requests for staging and prod deploys would add efficiency to our deploy process.
Since code review is now done in the adhoc repo, we could automatically open a PR against the HHS repo when a branch is merged to main in the Adhoc Repo. This would keep a manual approval gate for deployment to staging (approving and merging the PR) while automating more of the process.
After a successful deploy to staging we could automatically open a PR against the prod branch and could choose to deploy that whenever we would like.
The text was updated successfully, but these errors were encountered:
* renamed topics in constants
* update topics names function and test written
* update topics names function and test written
* comment and add to scheduled job
* fix failing frontend test
* use logger.info instead of console.log
* remove rename topics from cron
* install deps from main
* remove running job
* bump up the timeout
* reduce timeout
* nope, we need that timeout
Automating the creation of pull requests for staging and prod deploys would add efficiency to our deploy process.
Since code review is now done in the adhoc repo, we could automatically open a PR against the HHS repo when a branch is merged to main in the Adhoc Repo. This would keep a manual approval gate for deployment to staging (approving and merging the PR) while automating more of the process.
After a successful deploy to staging we could automatically open a PR against the prod branch and could choose to deploy that whenever we would like.
The text was updated successfully, but these errors were encountered: