formsort/Zero-waste Heroku Deploy
Deploy to Heroku with a repo tarball
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Jan 4, 2023
- License
- Apache 2.0
Pinned Snippet
uses: formsort/action-heroku-deploy@64c5a22488c50b1dea4e50c637d168da0efd3ebf # v1tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github_repo | GitHub repo name with owner (eg. formsort/formsort) | yes | — |
| github_token | GITHUB_TOKEN | yes | — |
| heroku_api_key | API Key for the Heroku account that will perform the deploy | yes | — |
| heroku_app_name | Name of the Heroku app to be deployed | yes | — |
| heroku_app_version | The new version of the app to be deployed. Will fall back to `inputs.ref` if not provided. | no | — |
| ref | Git ref to deploy to Heroku | yes | "" |
| only_promotion | Only allow promoting from a pipeline (rather than a direct build) | yes | false |
Outputs
| name | description |
|---|---|
| source_tarball | The URL of the source tarball used to create the build |
| build | The JSON blob of the build created by Heroku |
| build_id | The id of the build created by Heroku |
| build_log | The logs for the build created by Heroku |
| release | The JSON blob of the release created by Heroku |
| release_id | The id of the release created by Heroku |
| release_log | The logs for the release created by Heroku |