blocks|key|1074959|text|正常克隆存储库：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1074960|git+clone+git://github.com/rspec/rspec-tmbundle.git+RSpec.tmbundle|code-block|syntax|javascript|1074961|然后像这样签出你想要的标签：|1074962|git+checkout+tags/1.1.4|1074963|这将签出处于“分离的头”状态的标签。在这种状态下，“您可以环顾四周，进行实验性更改并提交它们，并通过执行另一次签出来丢弃这些提交，而不会影响任何分支”。|1074964|要保留所做的任何更改，请将其移动到新分支：|1074965|git+checkout+-b+1.1.4-jspooner|1074966|您可以使用以下命令返回到主分支：|1074967|git+checkout+master|1074968|请注意，正如本答案的第一个修订版中所提到的，还有另一种检查标记的方法：|1074969|git+checkout+1.1.4|1074970|但是正如在评论中提到的，如果你有一个同名的分支，这将导致git警告你refname是不明确的，并在默认情况下签出该分支：|1074971|warning:+refname+'test'+is+ambiguous.
Switched+to+branch+'1.1.4'|1074972|如果存储库不在分支和标记之间共享名称，则可以安全地使用速记。|1074973|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|18|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1C|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|1F|8|@]|9|@]|A|$]]|$1|W|3|X|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|Y|3|Z|5|6|7|1H|8|@]|9|@]|A|$]]|$1|10|3|11|5|D|7|1I|8|@]|9|@]|A|$E|F]]|$1|12|3|13|5|6|7|1J|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|15|$]]

Clone the repository as normal:

<pre><code>git clone git://github.com/rspec/rspec-tmbundle.git RSpec.tmbundle
</code></pre>

Then checkout the tag you want like so:

<pre><code>git checkout tags/1.1.4
</code></pre>

This will checkout out the tag in a 'detached HEAD' state. In this state, "you can look around, make experimental changes and commit them, and [discard those commits] without impacting any branches by performing another checkout".

To retain any changes made, move them to a new branch:

<pre><code>git checkout -b 1.1.4-jspooner
</code></pre>

You can get back to the master branch by using:

<pre><code>git checkout master
</code></pre>

Note, as was mentioned in the first revision of this answer, there is another way to checkout a tag:

<pre><code>git checkout 1.1.4
</code></pre>

But as was mentioned in a comment, if you have a branch by that same name, this will result in git warning you that the refname is ambiguous and checking out the branch by default:

<pre><code>warning: refname 'test' is ambiguous.
Switched to branch '1.1.4'
</code></pre>

The shorthand can be safely used if the repository does not share names between branches and tags.

blocks|key|860382|text|从Git+v2.23.0+(2019年8月)开始，当你只是切换分支/标签时，git+switch比git+checkout更受欢迎。我猜他们这样做是因为git+checkout有两个功能:切换分支和恢复文件。因此，在v2.23.0中，他们添加了两个新命令git+switch和git+restore，以分离这些问题。我预测在未来的某个时候，git+checkout将会被弃用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|860383|要切换到普通分支，请使用git+switch+<branch-name>。要切换到类似提交的对象，包括单个提交和标记，请使用git+switch+--detach+<commitish>，其中<commitish>是标记名或提交号。|860384|--detach选项强制您认识到您处于“inspection+and+discardable+experiments”模式。要从要切换到的成员创建一个新分支，请使用git+switch+-c+<new-branch>+<start-point>。|860385|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/git/git/blob/master/Documentation/RelNotes/2.23.0.txt|1|https://git-scm.com/docs/git-switch#Documentation/git-switch.txt---detach^0|12|A|1D|C|24|C|3J|A|3U|B|4Q|C|1|B|0|0|C|O|1Q|V|2O|B|0|0|8|2A|14|J|14|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@$9|16|A|17|1|18]]|E|$]]|$1|F|3|G|5|6|7|19|8|@$9|1A|A|1B|B|C]|$9|1C|A|1D|B|C]|$9|1E|A|1F|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1G|8|@$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]]|D|@$9|1L|A|1M|1|1N]]|E|$]]|$1|J|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]]|K|$L|$5|M|N|O|E|$P|Q]]|R|$5|M|N|O|E|$P|S]]]]

As of <a href="https://github.com/git/git/blob/master/Documentation/RelNotes/2.23.0.txt" rel="noreferrer">Git v2.23.0</a> (August 2019), <code>git switch</code> is preferred over <code>git checkout</code> when you’re simply switching branches/tags. I’m guessing they did this since <code>git checkout</code> had two functions: for switching branches and for restoring files. So in v2.23.0, they added two new commands, <code>git switch</code>, and <code>git restore</code>, to separate those concerns. I would predict at some point in the future, <code>git checkout</code> will be deprecated.

To switch to a normal branch, use <code>git switch &lt;branch-name&gt;</code>. To switch to a commit-like object, including single commits and tags, use <code>git switch --detach &lt;commitish&gt;</code>, where <code>&lt;commitish&gt;</code> is the tag name or commit number.

The <code>--detach</code> option forces you to recognize that you’re in a mode of <a href="https://git-scm.com/docs/git-switch#Documentation/git-switch.txt---detach" rel="noreferrer">“inspection and discardable experiments”</a>. To create a new branch from the commitish you’re switching to, use <code>git switch -c &lt;new-branch&gt; &lt;start-point&gt;</code>.

How do I check out version version/tag 1.1.4 of the <a href="https://github.com/rspec/rspec-tmbundle" rel="noreferrer">rspec bundle</a>?

<pre><code>cd ~/Library/Application\ Support/TextMate/Bundles/
git clone git://github.com/rspec/rspec-tmbundle.git RSpec.tmbundle
osascript -e 'tell app "TextMate" to reload bundles'
</code></pre>

Switch to another Git tag

如何查看的版本版本/标记1.1.4cd ~/Library/Application\ Support/TextMate/Bundles/git clone git://github.com/rspec/rspec-tmbundle.git RSpec.tmbundleosascript -e 'tell app "Te...

问切换到另一个Git标签
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问切换到另一个Git标签EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问切换到另一个Git标签
EN