Update README about new auto_tag logic #1
13
README.md
13
README.md
|
@ -14,14 +14,23 @@ Drone plugin uses Docker-in-Docker to build and publish Docker images to a conta
|
|||
|
||||
When pushing a tag and using `auto_tag: true`, the logic is below(Not implemented yet):
|
||||
|
||||
For git branches:
|
||||
|
||||
1) Tagging `main`` branch
|
||||
It will produce the tags: `dev`.
|
||||
2) Tagging `release/vxxx` branch
|
||||
It will produce the tags: `1.1x-dev`
|
||||
|
||||
For git tags:
|
||||
|
||||
1) Tagging a dev version which ends with `-dev`
|
||||
It will produce the tags: <original_tag>
|
||||
2) Tagging a pre-release version which ends with `-rcx`, `x` start from 1 to bigger number
|
||||
It will produce the tags: <original_tag>
|
||||
3) Tagging a latest stable release, we need to know if the version is the newest
|
||||
It will produce the tags: <original_tag>, 1, 1.1x, latest
|
||||
It will produce the tags: <original_tag>, `1`,`1.1x`, `latest`
|
||||
4) Tagging a low version stable release
|
||||
It will produce the tags: <original_tag>, 1.1x
|
||||
It will produce the tags: <original_tag>, `1.1x`
|
||||
|
||||
## Build
|
||||
|
||||
|
|
Reference in New Issue
Block a user