Github提前/后面指标的含义 [英] Meaning of Github Ahead/Behind Metrics

查看:144
本文介绍了Github提前/后面指标的含义的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

用简单的语言(希望有一个简单的例子),Github repo分支上的前后指标意味着什么?

分支和它正在接受的关注?是否落后于一个分支的坏迹象?

解决方案

前面是该分支上不存在的提交数量在基地分支上。 Behind是基本分支上不存在的提交数量。



前面和后面几乎就像一种年龄度量。前面的数字大概告诉您分支在合并基本分支时会产生多少影响。后面的数字告诉你自分支开始以来在基本分支上发生了多少工作。



我发现后面的数字对于判断分支是否可能干净地合并。当基本分支发生大量工作时,两个分支更有可能修改相同的行。当背后很大时,这是一个迹象表明,您应该将基本分支合并到此分支中进行同步。一旦你将基本分支合并到这个分支中,后面将是0。


In plain language (hopefully with a simple example), what do the ahead/behind metrics on a Github repo's branch mean?

And what are the implications for that branch and the attention it's receiving? Is being "behind" a bad sign for a branch?

解决方案

Ahead is the number of commits on this branch that do not exist on the base branch. Behind is the number of commits on the base branch that do not exist on this branch.

Ahead and behind are almost like a kind of "age" metric. The ahead number tells you roughly how much impact the branch will have on the base branch should it be merged. The behind number tells you how much work has happened on the base branch since this branch was started.

I find the behind number really useful for judging whether a branch is likely to merge cleanly. When a lot of work has happened on the base branch, it's more likely that the two branches have modified the same line(s). When behind is large, it's a sign that you should probably merge the base branch into this branch to sync up. Once you merge the base branch into this branch, behind will be 0.

这篇关于Github提前/后面指标的含义的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆