TortoiseGit是否真的让Git像TortoiseSVN一样易于使用？ [英] Does TortoiseGit actually make Git a lot easier to use like TortoiseSVN?

问题描述

随着TortoiseSVN的简单体验，我看了一些SVN的命令行，并且它不那么容易使用。 TortoiseGit是否真的让Git更容易使用，就像TortoiseSVN为SVN命令行做的一样吗？

我不知道认为应该对使用TortoiseGit偏好命令行git附加任何耻辱。毕竟，如果您在Windows中开发，那么您的文件系统主界面是通过Windows资源管理器。

TortoiseGit处理最常见的用例：检出，检查如果你发现你需要做的事情，那么它无法处理，然后回退到命令行可执行文件，但是对于你每天需要做的事情的98％ TortoiseGit中的工具来支持你。

特别是，考虑提交最新一组更改的行为。在TortoiseGit中，我的工作流程如下。我提交根文件夹并获取列出更改文件的窗口。然后，我可以逐个浏览这些内容，选择要执行的更改。一些更改可能是需要恢复的临时调整（一个简单的右键单击），一些是本地覆盖，不应该在存储库中，一些是可以安全删除的临时文件（再次，右键单击）等。对于其他人，我总是将修改后的文件与版本库中的版本进行比较（简单的双击）。这是一个有用的完整性检查，你知道你在做什么。例如，您可以删除任何临时调试代码或添加任何暂时被注释掉的代码。它还使您有机会退后一步并考虑更改的质量;例如，如果您添加了新方法但忘记添加文档注释，则可以在此阶段执行此操作。

对于这种工作流程，单个提交窗口比发射一堆单独的git命令简单得多。

With the easy experience of TortoiseSVN, I looked at some command line of SVN and it wasn't as easy to use. Does TortoiseGit actually makes Git a lot easier to use, just like TortoiseSVN did for the SVN command line?

解决方案

I don't think there should be any stigma attached to using TortoiseGit in preference to the command line git. After all, if you're developing in Windows then your primary interface with the file system is through Windows Explorer.

TortoiseGit handles the most common use cases: checking out, checking in, diffs, logs, etc. If you find something you need to do that it can't handle then by all means drop back to the command line executable, but for 98% of what you need to do on a daily basis there are tools in TortoiseGit to support you.

In particular, consider the act of committing your latest set of changes. In TortoiseGit, my workflow is as follows. I commit the root folder and get a window listing the changed files. I can then go through these one by one, choosing which changes to commit. Some changes may have been temporary tweaks that need reverting (a simple right-click), some are local overrides that should not be in the repository, some are temporary files that can be safely deleted (again, a right-click), etc. For the rest of them, I always diff the modified files against the versions in the repository (a simple double-click). This is a useful sanity check that you know what you're committing. For example, you can remove any temporary debugging code or add back anything that was temporarily commented out. It also gives you the chance to take a step back and consider the quality of your changes; for example, if you've added a new method but forgotten to add documentation comments you can do it at this stage.

For this sort of workflow, driving everything from a single commit window is a lot simpler than firing off a bunch of separate git commands.

这篇关于TortoiseGit是否真的让Git像TortoiseSVN一样易于使用？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！