Replies: 1 comment 1 reply
-
you mention a number of different approaches here, but it is hard to understand what your target is. a couple of things that i can confirm to move the conversation maybe a small step further:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In the past we polyrepos for our apps and used go-semrel-gitlab to handle the tagging/releases.
In this setup the "app" repo contains
develop
/staging
/production
branches and the app-services were git-submodules based offmaster
.Most projects have since moved to a monorepo structure (with the aforementioned branching approach) but a few of our projects cannot be changed to this due to their complexity.
In
go-semrel-gitlab
we had the option to create a pre-release such asand it will produce versions/tags of form
v1.2.3-staging.1
.This worked pretty well. Now, as
go-semrel-gitlab
hasn't been maintained for years I'd like to replace it withsemantic-release
.Normally we would configure the branches and set non-production branches to
prerelease: true
which end up creating a tag like that.However, in this particular instance we cannot do that since the services all have one branch.
Is there a way in
semantic-release
to handle this?Beta Was this translation helpful? Give feedback.
All reactions