Github Ahead/Behind 指标的含义 [英] Meaning of Github Ahead/Behind Metrics

问题描述

用简单的语言(希望有一个简单的例子)，Github 存储库分支上的超前/滞后指标是什么意思?

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 是此分支上不存在于基础分支上的提交数.后面是这个分支上不存在的基础分支上的commit数.

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.

我发现后面的数字对于判断一个分支是否可能干净地合并非常有用.当基础分支上发生了大量工作时，两个分支更有可能修改了同一行.当 behind 很大时，这表明您可能应该将基本分支合并到此分支中以进行同步.一旦你将基础分支合并到这个分支，后面就会是0.

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 Ahead/Behind 指标的含义的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！