If you like learning by “hacking Gui tools”, my advice for learning Git would be to try playing with MeGit/EGit since that way you will see more details that VS2022 is deliberately hiding. But my advice would be, sooner or later, you need to read some Git book since Git has its own terminology and philosophy of work, and if you ever get stuck with a problem with Git, like always, you need to know exactly what you are doing and what is the proper way to resolve the problem. And it will work up to a certain level, especially since VS2022 is deliberately hiding some Git concepts, like the staging of files (typical TFS-user question would be what is staging and why do I need it?). And especially those that are coming from other Version control systems, like TFS. I am sure that many developers will try to “hack their way into Git” just by playing with Git Gui options of VS2022. Though, they are showing more of it than VS2022. SourceTree designers, similar to VS2022 designers have chosen to hide part of “Git internals” like HEAD and Refs information. We think that MeGit/EGit a bit more powerful and better follows “Git philosophy” of work. We will show in parallel how its panels look compared with VS2022 for the same operations. But some power Git users might feel they are missing some tools/options or might feel that Git is not being done/presented in the proper way.ġ.3 SourceTree Git Gui client as a referenceĪtlassian SourceTree application is another popular Git Gui client. Maybe that was a smart approach that will bring many users/developers fast to the VS2022/Git platform due to the easy learning path. It looks like they believed that nasty Git details should be hidden as much as possible from the developers and the user interface simplified so developers with no knowledge of Git, but just basic knowledge of “Version control” concepts can use it and check-in (commit) their work locally and to the version control server. It seems they didn’t want to follow closely Git philosophy in all the details, like for example designers of MeGit/EGit did. īy looking at VS2022 Git Gui interface, I get the impression that its designers had their own view of how Git should look like. For example, I work with TFS for years and do everything from Gui and never used TFS command line. But also, the truth is maybe the user does not really need all those options in everyday work. Truth is that no Git Gui can offer all the options that the command line Git interface offers to the user. The real reference should be, of course, Git command line interface, but I find it too hard to read for the purpose of presentation for this article. So, I will use it as a reference, and to better present how Gui options could/might look like compared to VS2022 Gui “look and feel”. It is a Git Gui tool, but from all the Git Gui tools I have seen, this one is closest to “Git philosophy and terminology” and I like how it “looks and feels”.
I feel and is my strong opinion that standalone Git Gui client MeGit/EGit is “doing Git right”. 1.1 MeGit/EGit Git Gui client as a reference We plan to give a basic overview of GUI Git tools in VS2022 in this article. Git is integrated into Visual Studio IDE since version 2019, and with version 2022 it has got more features and is becoming Visual Studio/Microsoft’s favorite version control management tool. That will bring many developers to VS2022/Git platform faster but power users will need other tools too. Git inside VS2022 has a simplified interface compared to some other Git Gui clients, like MeGit/EGit and SourceTree. We are comparing Git functionality in Visual Studio 2022 IDE to other Git Gui clients.
0 kommentar(er)
