simontheleg/SemVer Tag from PR
Easily version your commits using PR labels
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| trunk | trunk of the repository | yes | main |
| label_major | label override for major changes | yes | merge-major |
| label_minor | label override for minor changes | yes | merge-minor |
| label_patch | label override for patch changes | yes | merge-patch |
| label_none | label override for none changes | yes | merge-none |
| repo_token | gh token with permissions contents.write and pull-requests.read | yes | — |
| repo_ssh_key | ssh-key to use for pushing tags, base64 encoded. Only needed when you want to trigger additional actions after the tag push. For detailed explanation see Readme | yes | — |
| repo_storage_path_overwrite | path where the repository is cloned. Defaults to GITHUB_WORKSPACE | no | — |
| should_set_tag | whether tag should be added to the cloned repo inside gh actions | yes | true |
| should_push_tag | whether tag should be pushed to the original repo | yes | true |
Outputs
| name | description |
|---|---|
| old-tag | the old tag before applying the semVer-bump |
| new-tag | the new tag after applying the semVer-bump |