Git flow is a great tool as a starter to teach people what a reasonable git workflow is. Once you understand got better, you may find it a bit constraining. Personally, I don't see why you shouldn't work out of master and make release tags. The develop branch seems like an extra step that is unnecessary. But I suppose if your team is quite large it makes sense. EDIT: Please not I am not suggesting that you not do fea…
Why aren't you using git-flow?
11–20 of 55 posts
Re: Why aren't you using git-flow?
#12Re: Why aren't you using git-flow?
#13Re: Why aren't you using git-flow?
#14Git flow is a great tool as a starter to teach people what a reasonable git workflow is. Once you understand got better, you may find it a bit constraining. Personally, I don't see why you shouldn't work out of master and make release tags. The develop branch seems like an extra step that is unnecessary. But I suppose if your team is quite large it makes sense. EDIT: Please not I am not suggesting that you not do fea…
If you develop directly in master, then how can you go back and fix a severe bug in the version of the code that is in your production site without having to revert all the in-progress development changes or risk introducing them into the bugfix? I believe this is the intent of not working in master. If you tag each release, does git allow you to checkout by that tag and then start making commits to it / make a new b…
If my edits grow to the point that I need to write tests or push to staging, I just checkout a feature branch before committing.
Re: Why aren't you using git-flow?
#15Git flow is a great tool as a starter to teach people what a reasonable git workflow is. Once you understand got better, you may find it a bit constraining. Personally, I don't see why you shouldn't work out of master and make release tags. The develop branch seems like an extra step that is unnecessary. But I suppose if your team is quite large it makes sense. EDIT: Please not I am not suggesting that you not do fea…
If you develop directly in master, then how can you go back and fix a severe bug in the version of the code that is in your production site without having to revert all the in-progress development changes or risk introducing them into the bugfix? I believe this is the intent of not working in master. If you tag each release, does git allow you to checkout by that tag and then start making commits to it / make a new b…
Re: Why aren't you using git-flow?
#16Git flow is a great tool as a starter to teach people what a reasonable git workflow is. Once you understand got better, you may find it a bit constraining. Personally, I don't see why you shouldn't work out of master and make release tags. The develop branch seems like an extra step that is unnecessary. But I suppose if your team is quite large it makes sense. EDIT: Please not I am not suggesting that you not do fea…
If you develop directly in master, then how can you go back and fix a severe bug in the version of the code that is in your production site without having to revert all the in-progress development changes or risk introducing them into the bugfix? I believe this is the intent of not working in master. If you tag each release, does git allow you to checkout by that tag and then start making commits to it / make a new b…
Re: Why aren't you using git-flow?
#17Earlier quoted context omitted.
If you develop directly in master, then how can you go back and fix a severe bug in the version of the code that is in your production site without having to revert all the in-progress development changes or risk introducing them into the bugfix? I believe this is the intent of not working in master. If you tag each release, does git allow you to checkout by that tag and then start making commits to it / make a new b…
I develop in master sometimes, but only check in small edits that are pushed immediately. If my edits grow to the point that I need to write tests or push to staging, I just checkout a feature branch before committing.
Re: Why aren't you using git-flow?
#18This is interesting. Does anyone know if it introduces any other metadata or concepts that are annoying if one reverts back to plain git?
Re: Why aren't you using git-flow?
#19http://wowcool.org/productlist.asp?id=s13 【 MTB】
http://wowcool.org/productlist.asp?id=n49 【Jordan 2010】
http://wowcool.org/productlist.asp?id=s44 【Watch】
http://wowcool.org/productlist.asp?id=s46 【Jewerly】
http://wowcool.org/productlist.asp?id=s45 【Sunglass】
http://wowcool.org/productlist.asp?id=s60 【Jean】
http://wowcool.org/productlist.asp?id=s53 【handbags】
http://wowcool.org/productlist.asp?id=s68 【Jacket】 The website wholesale for many kinds of fashion shoes, like the nike,jordan,prada,adidas, also including the jeans,shirts,bags,hat and the decorations. All the products are free shipping, and the the price is competitive, and also can accept paypal payment.,after the payment, can ship within short time hTtP://wWw.WoWcOoL.oRg
Re: Why aren't you using git-flow?
#20...you are "astounded" that some people never heard of some less-than-a-year-old add-on to a fashionable development tool.