We have a setupped branches like
Also using Git Flow for our project(s). Which really is great to have.
The thing is; when you finish a feature/hotfix, it's being merged to develop and master, which is great. Only I am wondering if it's also possible to include our test branch here too?
Can I just add "test = test" to the git config or is this not going to work either?
Thanks in advance.
If you are using gitflow, you should have 3 prefixes to work with: feature, hotfix, and release.
Feature should only merge to develop. Hotfix and Release should merge into both master and develop.
The point of "release" prefixed branches is to test. Instead of having a pre-defined permanent branch to deploy to your test site, I'd recommend deploying the current release/* branch to the test site. When there are failures, commit the fixes to the release/* branch. When the release is successfully validated, you finish it and it merges to develop and master.
Okay. We're working with Git Flow. We use the prefixes and we have a 'master', 'develop' and 'test' branch.
So; you're saying that a feature should be merged into 'test' manually (to test it) and when it's working, we should use Git Flows 'finish', which merges it into 'develop' and 'master'. And we should merge Hotfixes and Releases to test manually (to keep test up to date?)
Thanks for sharing your opinion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could do it that way, it would certainly work. However, my recommendation is to get rid of the permanent "test" branch, and INSTEAD deploy the current release or hotfix branch directly to your test site.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So you say; just make a clone on the "test" environment and just switch to the right branch instead of merging into a 'test' branch.. And only finish a hotfix or new feature when it's working on that?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is the design philosophy of git flow: http://nvie.com/posts/a-successful-git-branching-model/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.