如何在git gui中使用标签进行版本控制 [英] How to use tags for versioning in git gui
问题描述
我是一个完全彻底的noob，所以要温柔！
我使用git gui，并且从不碰触命令行界面。我是一个noob，和我一起工作的一些人甚至是noob-ey-er ...
当前状态：
- I在git hub上有一个仓库，其中包含一些脚本（以下称为'code'）
- 我正在使用git gui（mysysgit）
- 我已经提交了push's，并且对CVS有一个模糊的理解
b $ b - 我不相信我们需要分支
我觉得我应该能够使用标签来创建代码的版本。我还'觉得'在存储快照（或指向...的链接）的文件系统中应该有一个等效结构。
例如：
.\EdsLittleThing\v1.0
.\EdsLittleThing\v1.1
.\EdsLittleThing\v1.2 < >
等
然而，我无法弄清楚如何在git gui中创建一个标签。我可以找到的唯一标签引用似乎与合并分支绑定在一起，这对我没有帮助。
我搜索了网页，并且找不到一个参考如何使用Git Gui创建和管理版本。
我希望能够创建一个稍微简单的版本：
最后说明：虽然我被带到相信我的答案是在'tags'中找到的，我真的不在乎它的真正答案是否使用了修订版/分支/任何内容。 解决方案
p>您想要使用gitk，可通过Repository-> Visualize ...获得。
在顶部窗格中，右键单击要标记的提交，然后选择create tag 。
在git模型中，通常不会在同一个存储库下将标签签出到磁盘。你可以有多个版本库（全部从上游克隆）或者不同版本的多个工作目录，但是大多数情况下只需使用git的工具就可以避免同时检出多个版本。
你所建议的 与gitflow模型不同，所以我不建议使用它作为参考。阅读ProGit书籍， http://progit.org 以获得良好的建议和其他一些工作流程。我使用的是以上任何一种。
通常，您在主要里程碑处进行标记。当一段代码变成客户可见的时候，或者当我们准备好进入正式的质量保证实践的代码时，我会对其进行标记。通常不需要标记提醒事件发生的时间。这是提交消息的目的。
I'm a complete and utter noob, so be gentle!
I'm using git gui, and never touching the command line interface. I'm a noob, and some of the people i'm working with are even noob-ey-er...
Current state:
- I have a repository on git hub which contains a handful of scripts (henceforth 'code')
- I'm using git gui (mysysgit)
- I have made commits and push's and have a vague understanding of CVS
- I don't believe we will need to branch
I feel that I should be able to use tags to create versions of the code. I also 'feel' like there should be an equivelant structure in the filesystem where the snapshots (or links to...) are stored.
eg:
.\EdsLittleThing\v1.0
.\EdsLittleThing\v1.1
.\EdsLittleThing\v1.2
etc
However, I can not work out how to create a tag within git gui. The only tag reference i can find seems to be tied to merging branches, and that doesn't help me.
I have scoured the web, and can not find a single reference on how to create and manage versions using Git Gui.
I want to be able to create a slightly more simple version of this:
Final note: Whilst I'm led to believe that my answer is found in 'tags', I dont really care if its really answered by using revisions / branches / whatever.
You want to use gitk, available by Repository->Visualize…
In the top pane, right click on the commit you want to tag at, and select create tag.
In the git model, you do not typically have tags checked out to disk under the same repository. You could have multiple repositories (all cloned from upstream) or the not suggested multiple working directories at different revisions with one revision, but most times simply using git's tool obviates the need to have multiple versions checked out at the same time.
What you are suggesting is nothing like the gitflow model, so I don't recommend using that as a reference. Read the ProGit book, http://progit.org for good advice and a few other workflows. I use one which is none of the above.
Typically you tag at major milestones. I tag when a piece of code becomes customer visible, or when we have code ready to move into formal QA practices. There is typically no need to tag as reminders of when things happened. That is what commit messages are for.
这篇关于如何在git gui中使用标签进行版本控制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
