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
Currently, both the root template and template project manage to define all variables for GitHub workflows for both Production and Staging env in the same place Secrets > Action. Hence, we must manually name these variables with _PRODUCTION or _STAGING postfixes and can not really know which one belongs to each env or is being shared between them.
GitHub supports a feature to manage them in each environment called Environments. We should follow this approach to define them wisely.
Variables belonging to the app build will be moved to Environments.
Variables only be used for the workflow in both env will be kept in Secrets > Action.
Who Benefits?
Developers
The text was updated successfully, but these errors were encountered:
Why
Currently, both the
root template
andtemplate project
manage to define all variables for GitHub workflows for both Production and Staging env in the same place Secrets > Action. Hence, we must manually name these variables with_PRODUCTION
or_STAGING
postfixes and can not really know which one belongs to each env or is being shared between them.GitHub supports a feature to manage them in each environment called
Environments
. We should follow this approach to define them wisely.Environments
.Who Benefits?
Developers
The text was updated successfully, but these errors were encountered: