Skip to content

Documentation enhanced concerning issue #888 #2025

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
asbjornu merged 3 commits into from
Jan 7, 2020
Merged

Documentation enhanced concerning issue #888 #2025

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
329c67b
Documentation enhanced concerning issue #888 (https://github.com/GitT…
teneko Jan 7, 2020
aca18fc
Content <buildnumber> has been escaped to \<buildnumber>
teneko Jan 7, 2020
ba693af
Apply change suggestion `...-ci-<buildnumber>` in favour of "...-ci-\…
teneko Jan 7, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions docs/input/docs/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -137,6 +137,18 @@ When using `mode: ContinuousDeployment`, the value specified in
`continuous-delivery-fallback-tag` will be used as the pre-release tag for
branches which do not have one specified. Default set to `ci`.

Just to clarify: For a build name without `...-ci-<buildnumber>` or in other
words without a `PreReleaseTag` (ergo `"PreReleaseTag":""` in GitVersion's JSON output)
at the end you would need to set `continuous-delivery-fallback-tag` to an empty string (`''`):

```yaml
mode: ContinuousDeployment
continuous-delivery-fallback-tag: ''
...
```

Doing so can be helpful if you use your `master` branch as a `release` branch.

### tag-prefix

A regex which is used to trim git tags before processing (eg v1.0.0). Default is
Expand Down