it is A process called "git flow" but the ideas ca...
# random
c
it is A process called "git flow" but the ideas can be used for other schemes if needed
s
'git flow' is horribly over complicated for many use cases, including NetSuite scripting in my experience. My opinion of course, but based on years of success using both git flow and much simpler workflows with git.
c
Yeah there's several different workflows, and you don't have to use all of the pieces of gitflow but if you're learning, its a decent place to get started.
s
really? I think gitflow is an advanced workflow and not a good learning spot to get started. I've seen junior devs struggle with it mightily. They basically just follow it without really understanding it (at least in my direct experience). With NS code frankly I find working directly on master, with an occasional feature branch to be quite adequate and less error prone.
c
Thats more of an issue w/ the crappy dev rather than the workflow itself. A 1 branch scheme is perfectly fine if you're doing client dev and not worrying about a product. I tend to do a develop (sb) and master (prod) style so I can keep code separate and know whats in (or should be in) each environment.