You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
andprod => 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
The text was updated successfully, but these errors were encountered: