git - Committing a project commits to the solution, why?

Question

Whenever I commit a project in a solution, if I go to a Git Bash and do some git log, none of the commits are present in the project folder, however they're all present on the solution folder.

How is one supposed to do for having commits per project rather than for the solution ?

Should I just do everything by myself on the Git Bash rather than using the IDE ?

Answer 1

Should I just do everything by myself on the Git Bash rather than using the IDE ?

YES

you should.

And there are (IMO) good reasons to do so:

• if you switch your dev environment (e.g. drop VS and choose Eclipse), you still know your version control
• you could use version control not only from within VS but also for versioning things you don't edit with VS
• only the command line gives you the full functionality of Git. I don't know any tool that doesn't hide important parts of Git.
• YOU decide the repo structure, not the IDE (I could hardly believe that VS creates repos per-project or per-solution. Are you really serious with that? YOU should be the one creating a repo!)

Don't get me wrong: VS provides by far the best debugger I've ever seen.
But when it comes to version control, I trust the console.

Nobody else.

---

Some questions related to the Awesome-Command-Line-Vs-Crippled-Other-Tools topic:

• Is it a good practise to do version control from outside the IDE?
• Does netbeans ignore my git pre-commit hook?
• Can you interact with the index/staging area with TortoiseGit?
• Does TortoiseGit actually make Git a lot easier to use like TortoiseSVN?