4 ms·
Seeking advice from the git masters : I joined a new small team several weeks ago. All of us are fairly new to git, coming from cvs and svn backgrounds. We use
by jeffwass 8y ago
Seeking advice from the git masters :
I joined a new small team several weeks ago. All of us are fairly new to git, coming from cvs and svn backgrounds. We use Intellij as our primary IDE, and bitbucket as our remote origin.
Do y’all recommend using the IntelliJ git front end GUI, or calling git from the command line?
I thought I had a grasp of git from some side projects on GitHub, but now that it’s a key dev tool in our daily process, the more I learn about it and need to extend beyond simple checkout/commit/push workflow, the deeper the rabbit hole goes.
- peheje 8y agoLearn the git cmd prompt first. Use a text editor eg. Code to fix merges. Git is powerful. And can have a hard learning curve, but don't have to. Learn it in CMD. I mostly use status push pull commit -a add checkout checkout -b branch list merge Gitk and git GUI usually comes with most installations and works for Mac Windows Linux. Then any other UI is just sugar.
- chopin 8y agoIntelliJ is missing tooling for staging which I am missing. Imho the Eclipse tooling (EGit) is much better in that regard. I never had trouble mixing Eclipse and command line workflows whereas IntelliJ forces me more often to resort to the command line. As the sibling said, learning the command line first (and the model of Git) is mandatory, especially if you come from a CVS and SVN background. I came from Perforce and had a pretty hard time with Git until I invested two days with a good tutorial and much experimenting with two local and one remote repository. EDIT: spelling