如何确定 Git 分支的创建时间?
有没有办法确定 Git 分支的创建时间?
我的存储库中有一个分支,并且我不记得创建它,并且认为也许看到创建时间戳会唤起我的记忆。
Is there a way to determine when a Git branch was created?
I have a branch in my repository, and and I don't remember creating it and thought maybe seeing the creation timestamp would jog my memory.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(16)
正如评论中指出的 和 Jackub 的回答,只要您的分支比配置设置中设置的天数新
gc.reflogexpire
(默认为 90 天),然后您可以利用 reflog 来查找分支引用首次创建的时间。请注意,
git reflog
可以占用大部分git log
标志。还请注意,HEAD@{0}
样式选择器实际上是时间概念,实际上,它是作为日期字符串处理(以一种黑客方式)的。这意味着您可以使用标志--date=local
并获得如下输出:有时使用
--date=relative
也可能很有用:最后一个注意:
--all
标志(实际上是 git-reflog 理解的 git-log 标志)将显示refs/
中所有已知引用的引用日志(而不是简而言之,HEAD
),它将清楚地向您显示分支事件:As pointed out in the comments and in Jackub's answer, as long as your branch is younger than the number of days set in the config setting
gc.reflogexpire
(the default is 90 days), then you can utilize your reflog to find out when a branch reference was first created.Note that
git reflog
can take mostgit log
flags. Further note that theHEAD@{0}
style selectors are effectively notions of time and, in fact, are handled (in a hacked sort of way) as date strings. This means that you can use the flag--date=local
and get output like this:It may also be useful at times to use
--date=relative
:One last note: the
--all
flag (which is really a git-log flag understood by git-reflog) will show the reflogs for all known refs inrefs/
(instead of simply,HEAD
) which will show you branch events clearly:使用
如果您希望使用 gitk 在上下文中查看它,则使用
(其中 foo 是您要查找的分支的名称。)
Use
If you’d rather see it in context using gitk, then use
(where foo is the name of the branch you are looking for.)
Pro Git § 3.1 Git 分支 - 什么是分支Is 很好地解释了 Git 分支的真正含义:
由于分支只是一个轻量级指针,因此 Git 没有任何关于其历史记录或创建日期的明确概念。 “但是等等,”我听到你说,“Git 当然知道我的分支历史!”嗯,有点像。
如果您运行以下任一命令:
您将看到看起来像“分支的历史记录”的内容,但它实际上是可从“分支”访问但无法从master访问的提交列表。这会为您提供所需的信息,但当且仅当您从未将“branch”合并回master,并且自创建以来从未将master合并到“branch”中它。如果你们合并了,那么这种差异的历史就会崩溃。
幸运的是,转发日志通常包含您想要的信息,正如此处的各种其他答案中所解释的那样。使用此:
显示分支的历史记录。此列表中的最后一项(可能)是您创建分支的点。
如果分支已被删除,则“branch”不再是有效的 git 标识符,但您可以使用它来代替,这可能会找到您想要的内容:
或者在 Windows cmd shell 中:
请注意,reflog 在远程分支上无法有效工作,仅限您在本地处理过的内容。
Pro Git § 3.1 Git Branching - What a Branch Is has a good explanation of what a Git branch really is:
Since a branch is just a lightweight pointer, Git doesn't have any explicit notion of its history or creation date. "But hang on," I hear you say, "of course Git knows my branch history!" Well, sort of.
If you run either of the following:
you will see what looks like the "history of your branch", but it is really a list of commits reachable from 'branch' that are not reachable from master. This gives you the information you want, but if and only if you have never merged 'branch' back to master, and have never merged master into 'branch' since you created it. If you have merged, then this history of differences will collapse.
Fortunately, the reflog often contains the information you want, as explained in various other answers here. Use this:
to show the history of the branch. The last entry in this list is (probably) the point at which you created the branch.
If the branch has been deleted then 'branch' is no longer a valid git identifier, but you can use this instead, which may find what you want:
Or in a Windows cmd shell:
Note that reflog won't work effectively on remote branches, only ones you have worked on locally.
首先,如果您的分支是在
gc.reflogexpire
天内创建的(默认 90 天,即大约三个月),您可以使用git log -g
或git reflog show
查找 reflog 中的第一个条目,这将是创建事件,如下所示(对于git log -g
):会得到谁创建了一个分支,之前有多少次操作,以及来自哪个分支(好吧,它可能只是“从 HEAD 创建”,这没有多大帮助)。
这就是 MikeSep 在他的回答中所说的 。
其次,如果您的分支时间超过
gc.reflogexpire
并且已运行git gc
(或者它是自动运行的),则必须找到该分支的共同祖先它是从创建的。看一下配置文件,也许有branch..merge
条目,它会告诉你这个分支基于哪个分支。例如,如果您知道相关分支是从 master 分支创建的(从 master 分支分叉),则可以使用以下命令查看共同祖先:
您还可以尝试 git show-branch; master,作为替代方案。
这就是gbacon在他的回复中所说的 。
First, if your branch was created within
gc.reflogexpire
days (default 90 days, i.e., around three months), you can usegit log -g <branch>
orgit reflog show <branch>
to find the first entry in reflog, which would be the creation event, and looks something like below (forgit log -g
):You would get who created a branch, how many operations ago, and from which branch (well, it might be just "Created from HEAD", which doesn't help much).
That is what MikeSep said in his answer.
Second, if you have branch for longer than
gc.reflogexpire
and you have rungit gc
(or it was run automatically), you would have to find common ancestor with the branch it was created from. Take a look at config file, perhaps there isbranch.<branchname>.merge
entry, which would tell you what branch this one is based on.If you know that the branch in question was created off master branch (forking from master branch), for example, you can use the following command to see common ancestor:
You can also try
git show-branch <branch> master
, as an alternative.This is what gbacon said in his response.
我还不确定它的 Git 命令,但我想你可以在引用日志中找到它们。
我的文件中似乎有 Unix 时间戳。
打印日志时似乎有一个选项可以使用引用日志历史记录而不是提交历史记录:
您也可以跟踪此日志,回到创建分支时。不过,git log 显示的是提交日期,而不是您执行在引用日志中添加条目的操作的日期。除了查看上面路径中的实际引用日志之外,我还没有找到这一点。
I'm not sure of the Git command for it yet, but I think you can find them in the reflogs.
My files appear to have a Unix timestamp in them.
There appears to be an option to use the reflog history instead of the commit history when printing the logs:
You can follow this log as well, back to when you created the branch.
git log
is showing the date of the commit, though, not the date when you made the action that made an entry in the reflog. I haven't found that yet, except by looking in the actual reflog in the path above.试试这个:
Try this:
这为我做到了:(10年后)
由于没有存储有关分支创建时间的信息,所以它的作用是显示每个分支的第一次提交(
--no-walk< /code>),其中包括提交日期。对于远程分支使用
--remotes
,对于本地分支则省略它。由于我在创建另一个分支之前至少在一个分支中进行了一次提交,因此这允许我出于文档目的追溯几个月的分支创建(以及功能开发启动)。
来源: stackexchange 上的 AnoE
This did it for me: (10 years later)
Since there is no stored information on branch creation times, what this does is display the first commit of each branch (
--no-walk
), which includes the date of the commit. Use--remotes
for the remote branches, or omit it for local branches.Since I do at least one commit in a branch before creating another one, this permitted me trace back a few months of branch creations (and feature dev-start) for documentation purposes.
source: AnoE on stackexchange
用途:
显示当前文件夹中存储库的所有生命周期。
首先出现的分支名称(从下到上)是创建的源。
这意味着:
从 master 创建分支开发(checkout -b)
从开发创建分支 feature-jira35 (checkout -b)
从开发中创建分支 feature-jira-sut-46 (checkout -b)
Use:
to show all the living cycles of your repository in the current folder.
The branch name that first appears (from down to up) is the source that was created.
That means:
Branch development is created (checkout -b) from master
Branch feature-jira35 is created (checkout -b) from development
Branch feature-jira-sut-46 is created (checkout -b) from development
如何通过 GitHub GUI 知道
我显示了所有答案,但没有人通过 UI 给出答案。如果有人想通过 GitHub UI 查看分支何时创建。
您可以看到分支创建如下
How to know via the GitHub GUI
I show all the answers and no one gave an answer with the UI. If anyone likes to see when the branch is created via the GitHub UI.
You can see the branch creation like as below
句法:
<代码>
git reflog --date=本地 | grep 结帐: | grep ${当前分支} |尾部-1
示例
:
<代码>
git reflog --date=本地 | grep 结帐: | grep dev-2.19.0 | grep dev-2.19.0 | grep dev-2.19.0尾部-1
结果
:
<代码>
cc7a3a8ec HEAD@{Wed Apr 29 14:58:50 2020}:结帐:从 dev-2.18.0 移动到 dev-2.19.0
syntax:
git reflog --date=local | grep checkout: | grep ${current_branch} | tail -1
example:
git reflog --date=local | grep checkout: | grep dev-2.19.0 | tail -1
result:
cc7a3a8ec HEAD@{Wed Apr 29 14:58:50 2020}: checkout: moving from dev-2.18.0 to dev-2.19.0
此命令显示 main 中分支 dev 的创建日期:
输出:
This command shows the creation date of branch dev from main:
Output:
这是我在发现这个问题之前想到的。
This is something that I came up with before I found this question.
我找到了最好的方法:
我总是检查通过这种方式创建的最新分支
I found the best way:
I always check the latest branch created by this way
结合 Andrew Sohn 的回答< /a>:
Combined with the answer from Andrew Sohn:
如果您想获取所有分支机构的详细信息
If you want to get the details for all the branches
如果只是检查原始修订版的 SHA-1 哈希值:
(来源)
它可以简化并使用
git log -- oneline master..修复
。If it is just checking the SHA-1 hash value of the original revision:
(Source)
It could be simplified and use
git log --oneline master..fix
.