blocks|key|389322|text|你没有丢失它，Git仍然保留着一份副本(但目前任何分支都无法访问它)。您可以使用git+reflog命令查找丢失的提交。reflog跟踪分支头的历史位置，您可以使用它来查找分支头之前所指向的内容。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|389323|entityMap^0|14|A|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

You did not lose it, Git still keeps a copy (but it is currently unreachable by any branch head). You can find your missing commit using the <code>git reflog</code> command. The reflog keeps track of the historical positions of a branch head, and you can use it to find things that the branch head was pointing at previously.

blocks|key|605416|text|旧的提交仍在reflog中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|605417|git+reflog|code-block|syntax|javascript|605418|这将显示一个提交列表，“丢失的”提交应该在其中。你可以把它变成一个新的分支。例如，如果SHA-1是分支，那么您可以在旧的提交处创建一个名为“ba5a739+-ba5a739”的新分支，方法是：|605419|git+branch+new-branch+ba5a739|605420|请注意，当数据库被修剪时，“丢失的”提交将被删除。|605421|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The old commit is still in the reflog.

<pre><code>git reflog
</code></pre>

This will show a list of commits, and the "lost" commit should be in there. You can make it into a new branch. For example, if the SHA-1 is ba5a739, then you can make a new branch named "new-branch" at the old commit with:

<pre><code>git branch new-branch ba5a739
</code></pre>

Note that "lost" commits will get deleted when the database is pruned.

blocks|key|605503|text|在Sourcetree中，我发现git+reflog不起作用，所以我想出了如何使用GUI来做到这一点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|605504|首先，尝试通过在命令历史记录中查找一条消息来查找“丢失的”提交(查看:显示命令输出)。在您丢失的提交之后，它有望出现在命令"Switching+Branch“中，并且您将看到带有1234567提交ID的提交注释。|605505|将提交ID带到下一步。|605506|点击顶部工具栏中的"Branch“按钮，您应该会看到一个对话框"New+Branch”，您可以在其中指定某个提交。将提交ID放入其中，指定一个新的分支名称，点击Create+branch，您应该会得到一个包含丢失的提交的新分支！|605507|这为我找回了一些丢失的工作！|605508|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

In Sourcetree, I found that git reflog didn't work, so I figured out how to do this using the GUI.

First, try to find the "lost" commit by looking for a message in the Command History (view:Show Command Output). It'll hopefully be in the command "Switching Branch" after the commit that you lost and you'll see the commit comment with a 1234567 commit ID.

Take that Commit ID to next step.

Hit the "Branch" button in the top toolbar and you should get a dialog "New Branch" where you can specify a certain commit. Put that Commit ID in there, specify a new branch name, hit Create Branch and you should get a new branch with your lost commit! 

This brought back some lost work for me!

blocks|key|605598|text|使用以下命令，您可能会发现丢失(悬空)的提交：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|605599|git+fsck+--lost-found|code-block|syntax|javascript|605600|请注意，如果您当前的头是悬空提交，则不会将其列为丢失。|605601|你可以在git-fsck(1)+Manual+Page上找到更多信息|offset|length|605602|然后，您可以在丢失的提交上创建分支：|605603|git+branch+new-branch+ba5a739|605604|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/docs/git-fsck^0|0|0|0|4|N|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|11|8|@]|9|@$K|12|L|13|1|14]]|A|$]]|$1|M|3|N|5|6|7|15|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

You may find lost (dangling) commits with the following command:

<pre><code>git fsck --lost-found
</code></pre>

Note, if your current head is dangling commit, it is not listed as lost.

You may find more info at <a href="http://git-scm.com/docs/git-fsck">git-fsck(1) Manual Page</a>

Then you may create branch on that lost commit:

<pre><code>git branch new-branch ba5a739
</code></pre>

This is what happened:

I have a branch A. On branch A I committed a bunch of changes. I was not happy with the code, so I checked out the previous commit in branch A. I then made a bunch more changes and committed them on branch A. Now I can not find this commit anywhere. Did I lose this code?

What happens to git commits created in a detached HEAD state?

数据库

事情是这样的：我有一个分支A。在分支A上，我提交了一系列更改。我对代码不满意，所以我在分支A中签出了以前的提交，然后我又做了一些更改，并在分支A上提交了它们。现在，我在任何地方都找不到这个提交。我是不是弄丢了这个代码？

问在分离的头状态下创建的git提交会发生什么？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在分离的头状态下创建的git提交会发生什么？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在分离的头状态下创建的git提交会发生什么？
EN