Instead of using the tag, you can create a release branch which removes the need for a dev branch. How do you manage bug fixes to your master release and propagating those changes back into dev?
Instead of using the tag, you can create a release branch
Yes, we create branch from the tag in case a version needs patching.
which removes the need for a dev branch
Um no. Put another way, our dev branch uses the same pull request flow but longer lived.
How do you manage bug fixes to your master release and propagating those changes back into dev?
Bug fixes are squash merged from the pull request branches into master, then the dev branch rebase from master.
Yes I understand. I didn’t realise you were gutted a release branch from master as well, I understood you were just using the git tag!
Off topic, I've been to Belfast twice. Nice city!
It is, come back soon!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Instead of using the tag, you can create a release branch which removes the need for a dev branch. How do you manage bug fixes to your master release and propagating those changes back into dev?
Yes, we create branch from the tag in case a version needs patching.
Um no. Put another way, our dev branch uses the same pull request flow but longer lived.
Bug fixes are squash merged from the pull request branches into master, then the dev branch rebase from master.
Yes I understand. I didn’t realise you were gutted a release branch from master as well, I understood you were just using the git tag!
Off topic, I've been to Belfast twice. Nice city!
It is, come back soon!