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
Now, the generated project's CircleCI config publishes the app to the default release channel on master branch merges.
We generally use a staging / production deployment flow, so at least the app should publish to the staging release channel on merges to master and to the production release channel on merges to production. This shouldn't be asked to the user.
Additionally, we should ask the user if he wants to send the cloud instruction to Expo to build the .ipa and .aab binaries after publishing the production app.
All of these configurations should be written in the CircleCI config file
The text was updated successfully, but these errors were encountered:
Now, the generated project's CircleCI config publishes the app to the default release channel on
master
branch merges.We generally use a staging / production deployment flow, so at least the app should publish to the
staging
release channel on merges tomaster
and to theproduction
release channel on merges toproduction
. This shouldn't be asked to the user.Additionally, we should ask the user if he wants to send the cloud instruction to Expo to build the
.ipa
and.aab
binaries after publishing the production app.All of these configurations should be written in the CircleCI config file
The text was updated successfully, but these errors were encountered: