I’m a long time Eclipse user but new to Git/Egit. Recently I’ve been trying to use Egit because I want to use GitHub to collaborate with a number of projects. The projects I want to work on are not Eclipse-specific projects but I’d still like to set up a workflow so that I can work on them in Eclipse.
It seems that there are a number of things that need to fit together:
- The remote repository (on GitHub)
- The local repository (somewhere on my filesystem)
- The Git working directory
- The Eclipse project that I want to work in (including stuff outside the source tree like Eclipse project files, Maven config, build folders etc.)
How do these relate to each other and what should be my workflow?
In particular:
- Do I actually need a local repository or can I just work directly with the remote repository (like with SVN)?
- Can the Git working directory also be the Eclipse project? Or is this a bad idea?
- What should my workflow of push/pull/fetch etc. normally be?
- If I use Maven for dependency management in the Eclipse project, but don’t want all the Maven-specific stuff to get committed to SCM, can this work?
Guess I’m loking for some sound advice from someone who’s successfully made this work!
Git is all about working on a local repository and pushing elsewhere when necessary.
If it lines up this way, then yes. This is how I’ve managed my projects.
You push when you feel you have made enough commits (sometimes only 1) that are worth pushing. You pull when you want to work with changes that other people have pushed.
See gitworkflows for the official doc on different types of workflows.
Usually you just commit the pom.xml. Anything else is a user specific setting. Although, if I clone your repository and can’t do a “mvn compile”, then there’s something wrong.