actions/semantic-version
6
0
Fork 0
mirror of https://github.com/PaulHatch/semantic-version.git synced 2025-12-27 13:08:17 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Clarify namespace for new user

Browse source 
It took a bit to figure out how namespace works.  This minor addition helps me with clarification; feel free to disagree with that opinion. :D
This commit is contained in:
Danny Sauer 2021-01-25 17:09:13 -06:00 committed by GitHub
parent 12cce3bff2
commit 13e0565bfd
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 7 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
readme.md
View file

@ -115,15 +115,17 @@ not increase the `increment` output. In addition, if there are no changes in
a given commit with this path specified, the `changed` value will be false.
Second, the input `namespace` can be set to create an additional named version.
If this value is set, it will be appended to the end of tags for the version,
and only tags with this value appended will be considered when determining the
version.
If this value is set, it will be appended (separated by a hyphen) to the end of
tags for the version, and only tags with this value appended will be considered
when determining the version. The namespace will be pruned from the string
output as "version" within the action.
Finally, set different values for `major_pattern` and `minor_pattern` than the
other projects in order to be able to mark these commits independently.
To use secondary versions in a workflow, simply create additional steps in a
job referencing semantic version multiple times. For example:
job referencing semantic version multiple times. For example, a project tagged
like `v1.2.3+0-db` could be configured like this:
```yaml
- name: Application Version