#Github flow code
anything in the master branch is deployable - does that perhaps only ring true if the code has been through QA etc? So, is it that I have misunderstood the first point of GitHub Flow - i.e. At this stage, based on Github Flow's flow, if that user took a branch from Master they would include the changes that actually at this point in time are still in the QA environment. In the meantime, someone else may need to work on something completely different. We deploy to UAT/QA environments, where that release may remain for 3-4 weeks, depending on how long it takes the client and/or us to sign everything off.
Having looked at GitHub Flow, this seems a pretty straight forward option that would meet our needs - however it does seem to have a flaw that I'd like peoples opinions on.Īnything in the master branch is deployable.
We work on perhaps 20 different projects in total, and each project may only have releases every 2 months or so. In my opinion, GitFlow is overly complicated for our requirements. We're at the stage where we really want to consider our branching strategy and hence I've been doing some research. We've tried to learn as much as is possible by using GitBash so we can get under the core of git. We've been using it for about 6 months and have used GitHub and BitBucket.
0 kommentar(er)
