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
At the moment we can deploy only to the staging and prod environment together in our cd and auto_deploy workflows without the choice to deploy only to the staging environment.
Also, auto-deploy is triggered on merge and running deploying to the prod (without running release, example), so every merge the release is deployed to the prod without running release itself.
My proposal is:
auto_deploy on merging will deploy only to the staging,
cd can be triggered manually with the choice to deploy on the staging only or to both, as we already have in blockchain-api,
release triggering only manually and running cd with deploying to staging and prod.
The text was updated successfully, but these errors were encountered:
At the moment we can deploy only to the staging and prod environment together in our
cd
andauto_deploy
workflows without the choice to deploy only to the staging environment.Also,
auto-deploy
is triggered on merge and running deploying to the prod (without runningrelease
, example), so every merge the release is deployed to the prod without running release itself.My proposal is:
auto_deploy
on merging will deploy only to the staging,cd
can be triggered manually with the choice to deploy on the staging only or to both, as we already have in blockchain-api,release
triggering only manually and runningcd
with deploying to staging and prod.The text was updated successfully, but these errors were encountered: