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

version sequence per branch #572

Open
jahead opened this issue Apr 15, 2020 · 0 comments
Open

version sequence per branch #572

jahead opened this issue Apr 15, 2020 · 0 comments

Comments

@jahead
Copy link
Contributor

jahead commented Apr 15, 2020

Hey guys,

With this now being able to be used for non-js projects.
We were wondering if we could use this to manage our server environments.

Use case

Master is a common template for a service
Each branch is checked out from a master and one-to-one to a server environment where non-secret variables are set.
E.G environment-specific variables in the settings.py in django.

The problem

Obviously the changelog problem is still a problem (but can fix that with .gitattributes or different CHANGELOG files).
We are mostly interested in having separate version lines for each environment
We currently are using --prefix-tag as we figured that could solve our version tag conflict problem, but we are getting an issue when we 'sync' (merge) from the master, the standard-version is getting confused even though master => master/v1.0.1 and prod => pro/v1.0.2

it appears to ignore the --prefixTag when calculating the next version

If anyone has any extra information, or if your willing to let us patch this, please let us know.

Thanks,
Joshua Head

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant