[CI] Run CORE tests in GitHub Actions #61
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # This workflow will run whenever a PR is opened or changed. | ||
| # | ||
| # It will run tests and a few safety checks. | ||
| # | ||
| # If everything passes it can be set to auto-deploy to your staging app on Heroku. | ||
| # | ||
| # This workflow is primarily meant to be triggered automatically, but it can be run manually. | ||
| name: " 💻 PR CI (staging)" | ||
| on: | ||
| workflow_dispatch: | ||
| pull_request: | ||
| types: [opened, synchronize, reopened] | ||
| jobs: | ||
| mini_test: | ||
| name: 🧪 Minitest | ||
| uses: ./.github/workflows/_run_tests.yml | ||
|
Check failure on line 17 in .github/workflows/ci-cd-pipeline.yml
|
||
| secrets: inherit | ||
| standardrb: | ||
| name: 🔬 Standardrb | ||
| uses: ./.github/workflows/_standardrb.yml | ||
| secrets: inherit | ||
| db_schema: | ||
| name: 🔎 DB Schema | ||
| uses: ./.github/workflows/_database_schema_check.yml | ||
| secrets: inherit | ||
| # If you'd like to auto-deploy to your staging environment you can uncomment this next block. | ||
| # You'll need to set HEROKU_EMAIL and HEROKU_API_KEY in your repo secrets. | ||
| # Be sure to set the app name correctly below. | ||
| # deploy: | ||
| # name: 🚢 Deploy to Heroku | ||
| # uses: ./.github/workflows/_deploy_heroku.yml | ||
| # needs: [mini_test, standardrb, db_schema] | ||
| # secrets: inherit | ||
| # with: | ||
| # heroku-app-name: "" | ||
