-
-
Save swanson/527e20ea124c6896e9a0ca20a60c0d3e to your computer and use it in GitHub Desktop.
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
name: Deploy | |
on: | |
workflow_run: | |
workflows: [CI Build] # change this to match your build workflow name | |
types: [completed] | |
branches: [main] | |
jobs: | |
deploy: | |
runs-on: ubuntu-latest | |
environment: | |
name: your-environment-name-here | |
url: https://your-app.example.com | |
name: Deploy demo | |
if: ${{ github.event.workflow_run.conclusion == 'success' }} | |
steps: | |
- uses: actions/checkout@v2 | |
with: | |
fetch-depth: 0 | |
- name: Push to Heroku | |
run: git push -f https://heroku:$HEROKU_API_KEY@git.heroku.com/$HEROKU_APP_NAME.git main | |
env: | |
HEROKU_API_KEY: ${{ secrets.HEROKU_API_KEY }} | |
HEROKU_APP_NAME: your-heroku-app |
I think it's the presence of
environment
You are right.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
this is not really important, but eye catching:
naming job
deployment
instead ofdeploy
adds some kind of progressbar + text: deploying to