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
Remove unused templates since it's out of date and unmaintained, the team need to reference to git-template as single source truth and latest update for new projects:
Remove unused templates since it's out of date and unmantainced, the team need to reference to git-template as single source truth and latest update for new projects:
@hoangnguyen92dn Instead of remove, IMO, we should keep them up to date or have a script to sync them when generating new projects.
Revamp the deployment workflow: deploy_staging_and_production_to_firebase_app_distribution.yml. Github supports environment for deployment therefore creating variables/secretes with environment suffix is unnecessary
Agree, we should separate Environment variables by env: production and staging instead of by template: template-compose and template-xml.
Why
There are some points to revamp the current CI/CD template to have workflow ready to work in new projects:
https://github.com/nimblehq/android-templates/tree/develop/.cicdtemplate/.github
review_pull_request.yml
&&run_detekt_and_unit_tests.yml
. Both workflow have the same steps can be extract to shared workflow to reuse (Reference: https://docs.github.com/en/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization).deploy_staging_and_production_to_firebase_app_distribution.yml
. Github supports environment for deployment therefore creating variables/secretes with environment suffix is unnecessary (Reference: https://docs.github.com/en/actions/deployment/targeting-different-environments/using-environments-for-deployment)Who Benefits?
Developers
The text was updated successfully, but these errors were encountered: