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
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:
main
release-candidate
develop
Development is done via feature branches off develop which are merged back into develop. When ready, a new release candidate is created. This is merging develop into release-candidate branch. The release-candidate automatically 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 into release-candidate,
What I want to happen is the following:
On any commit/PR into release-candidate, release-candidate gets built with a version like 0.1.0-rc.4 which will increment every commit (e.g. 0.1.0-rc.5, 0.1.0-rc.6 etc)
When release-candidate gets merged into main, main should update the Minor version, e.g. 0.1.0-rc.6on release-candidate merges intomainand thenmainbuilds with version0.2.0`
Any hotfixes into main will advance patch (e.g. 0.2.0 becomes 0.2.1
I 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:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
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