Skip to content

Conversation

@KiLLeRRaT
Copy link
Contributor

Otherwise the branch name variable can never be used in any SemVer spec since it can contain a / when using nested branches.

My reasoning to just always replace it is that people will only use the branch name variable when trying to put together a GitVersion tag, which should be SemVer compliant. So no need to make this setting driven or introduce a new variable just for this.

Cheers,

…anch name variable can never be used in any SemVer spec since it can contain a / when using nested branches.
@Skoucail
Copy link
Contributor

Skoucail commented Jan 2, 2020

The BranchName variable has not direct connection with the SemVer.
If people are using the BranchName variable to do checks or reporting this change will break those setups.
Its only the SemVer spec that doesn't allow most special chars.
Variables like BranchName, InformationalVersion, etc all have no problem with those chars.

@Skoucail
Copy link
Contributor

Skoucail commented Jan 3, 2020

The issue will be resolved in #2014

@KiLLeRRaT
Copy link
Contributor Author

@Skoucail Excellent, thank you for that! You can then close this PR.

Cheers,

@asbjornu asbjornu closed this Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants