actions-marketplace-validations/GitHub Actions Create Tag
Bump and push git tag on merge
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| github_token | Required for permission to tag the repo. | yes | — |
| default_bump | Which type of bump to use when none explicitly provided (default: `patch`). | no | patch |
| tag | Tag name (default: `0.0.1`). | yes | v0.0.1 |
| release_branches | Comma separated list of branches (bash reg exp accepted) that will generate the release tags. Other branches and pull-requests generate versions postfixed with the commit hash and do not generate any tag. Examples: `master` or `.*` or `release.*,hotfix.*,master`... | no | master |
| create_annotated_tag | Boolean to create an annotated tag rather than lightweight | no | false |
| dry_run | Do not perform tagging, just calculate next version and changelog, then exit | no | false |
Outputs
| name | description |
|---|---|
| new_tag | Generated tag |
| latest_hash | latest commit hash |
| previous_tag | Previous tag (or `0.0.0`) |
| changelog | The conventional changelog since the previous tag |