dolittle/Establish Context
Establishes the context for the pipeline
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Dec 5, 2022
- License
- MIT
- Runtime
- Deprecated runtime
Pinned Snippet
uses: dolittle/establish-context-action@8462e2fecc7a21e2743afb332de5eae1b7c0f682 # v2.5.7tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| token | Token to use for Github API | yes | ${{ github.token }} |
| prerelease-branches | A comma-separated list of branch names that when merged a PR to will trigger a release. | yes | "" |
| environment-branch | If the build pipeline is for a target environment (e.g. development, test, staging) you'd specify that here. | no | "" |
| current-version | If the version is known, you can specify it with this | no | "" |
| version-file | If the version is in a file adhering to the expected JSON format, use this. | no | "" |
Outputs
| name | description |
|---|---|
| should-publish | Whether or not the pipeline should publish |
| current-version | The current version of the repository based on tags or 1.0.0 if there are no version tags |
| release-type | The type of the release. One of [major, minor, patch, prerelease] |
| cascading-release | Whether the publish was triggered by a cascading release. |
| pr-body | The body of the pull request |
| pr-url | The url to the pull request |