Replies: 1 comment
-
|
I’d suggest starting with the following configuration: workflow: TrunkBased/preview1with branch:
This setup follows a trunk-based development approach without the need of creating tags. Link[1]: TrunkBased/preview1.yml |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This should be really simple but I cannot get it working on even a very basic example repo.
We're us a flavour of GitFlow, so the branches look like this:
Development is done via feature branches off
developwhich are merged back intodevelop. When ready, a new release candidate is created. This is mergingdevelopintorelease-candidatebranch. Therelease-candidateautomatically builds and deploys builds on any PR to the testing team. Any bug fixes are done via bug branches (bug/12345/fix-a-bug) merged back intorelease-candidate,What I want to happen is the following:
release-candidate,release-candidategets built with a version like0.1.0-rc.4which will increment every commit (e.g.0.1.0-rc.5,0.1.0-rc.6etc)release-candidategets merged intomain,main should update the Minor version, e.g.0.1.0-rc.6on release-candidate merges intomainand thenmainbuilds with version0.2.0`mainwill advance patch (e.g.0.2.0becomes0.2.1I don't want to have to tag commits to advance the version.
This is the current config that seems to work correctly for everything apart from advancing the version as desired on
main:Any help would be massively appreciated.
Beta Was this translation helpful? Give feedback.
All reactions