fgerthoffert/Docker Shorthand Tags
Generate shorthand tags from semver releases present in a Docker repository repository (1.2.3 => 1 & 1.2)
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| src_registry | Source Docker registry (e.g. dockerhub, github) | yes | — |
| src_repository | Source Docker repository (e.g. user/repo) | yes | — |
| src_username | Username to connect to the source registry | yes | — |
| src_secret | Secret to connect to the source registry (password or token) | yes | — |
| dst_registry | Destination Docker registry (e.g. dockerhub, github) | yes | — |
| dst_repository | Destination Docker repository (e.g. user/repo) | yes | — |
| dst_username | Username to connect to the destination registry | yes | — |
| dst_secret | Secret to connect to the destination registry (password or token) | yes | — |
| dev_cache | Enable development cache, this prevents the action from fetching data from the source registry too frequently during development | no | false |
| version_digits_count | Number of version digits to include in the shorthand tags (for example 3 for 1.2.3 or 4 for 1.2.3.4) | no | 3 |
| snapshot_suffix | Suffix for which shorthands should be created (for example 1-SNAPSHOT and 1.2-SNAPSHOT for 1.2.3-SNAPSHOT) | no | -SNAPSHOT |
| dry_run | Enable dry run mode, this prevents the action from making any changes to the target registry during development. Will output the docker commands instead of executing them | no | true |
| create_latest | Enable creation of latest tags (e.g. latest) for most recent (highest digit) release pushed | no | false |
Outputs
no outputs