Release and merging back to development #2187
Unanswered
freakzlike
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey folks,
I am currently working on a release workflow for a web app.
My current workflow:
Default branch is
development
where features, fixes etc. get merged, It has a CI pipeline for tests, lints and deployment to development server. When releasing a new version, the changes get merged intorelease
branch. The CI of therelease
branch gets triggered and runssemantic-release
to update the version number, write change logs, push these changes torelease
and publish the package.Now the
release
branch is one commit ahead of thedevelopment
branch and I have to merge it back todevelopment
.Is there any other solution, which will avoid the merge back to
development
?It should also be possible to add a
staging
branch in between so the workflow would bedevelopment
->staging
->release
.Beta Was this translation helpful? Give feedback.
All reactions