4 ms·
I think this is the right response. OP is complaining about the workflow/process not about the tool. Instead of all that big process described, the team could
by dyingkneepad 6y ago
I think this is the right response.
OP is complaining about the workflow/process not about the tool. Instead of all that big process described, the team could simply git-clone upstream, work on their local main (formerly master) branches, then "git commit && git push && git pull" all the time and that's it: you got your old workflow back, but now with git.
- JacKTrocinskI 6y agoI think you guys hit the nail on the head here, we want our old workflow back! I'm not saying that the commit to master workflow is the greatest in the world but it worked for us and now we're blaming Git for this feature branch workflow which we admittedly we also tried with SVN but ended reverting back to the simple commit to trunk workflow.
- mcv 6y agoThere's a good chance that your employer switched to git because they want to enable feature branches and code review on pull requests.