To reduce the number of vendors required to manage the Lansing Codes software and simplify access control to builds and deployments, let's migrate the deployment pipeline from CircleCI to GitHub Actions.
The existing CircleCI configuration can be found in .circleci/config.yml. The pipeline should include these steps:
- For all branches, perform a build:
- Checkout code
npm ci
npm rebuild
npm test
- If the build succeeds on the
main branch, deploy to Heroku
@egillespie can set any environment variables required for the Heroku deployment.
To reduce the number of vendors required to manage the Lansing Codes software and simplify access control to builds and deployments, let's migrate the deployment pipeline from CircleCI to GitHub Actions.
The existing CircleCI configuration can be found in
.circleci/config.yml. The pipeline should include these steps:npm cinpm rebuildnpm testmainbranch, deploy to Heroku@egillespie can set any environment variables required for the Heroku deployment.