Skip to content
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.

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

Ignore numbers in release branch #1811

Closed
gthvidsten opened this issue Sep 12, 2019 · 3 comments
Closed

Ignore numbers in release branch #1811

gthvidsten opened this issue Sep 12, 2019 · 3 comments
Labels

Comments

@gthvidsten
Copy link

This is very similar to #1500 / #1541 , but sort of in a reverse sense.

The team I'm on use a flow similar (but not identical) to "gitflow". Our release branches gets PRs from feature branches. Seeing as one feature branch may require a 0.0.1 version update, and another branch requires a 0.1.0 verison update (based on the major/minor/patch-version-bump-message commit messages), and I don't know in advance which features are part of the next release, I therefore don't know which version number the next release will have and can't name it accordingly. I therefore want to just name them sequentially.
However, if I create a release branch called release/42.1 (a hotfix for release/42) this will be versioned as 42.1.0, whereas I would like the version of this to be the next logical version .

How can I get GitVersion to ignore the numbers in release branches?

@stale
Copy link

stale bot commented Dec 11, 2019

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Dec 11, 2019
@asbjornu
Copy link
Member

Perhaps you can figure out a regex pattern that matches your release-branches and then declare them as not being release branches with is-release-branch: false?

@stale stale bot removed the stale label Dec 11, 2019
@stale
Copy link

stale bot commented Mar 10, 2020

This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 10, 2020
@stale stale bot closed this as completed Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants