如何解决origin/master 比 upstream/master 领先 n,但 HEADS 相同
我从上游 master 拉取并推送到 origin master(在 GitHub 中)。在 Github 中说这个分支比
sdiff <(git log --oneline upstream/master) <(git log --oneline master)
去:
> a6ef172176 WIP
3153b6c723 [ci skip] Merge PR 29662 3153b6c723 [ci skip] Merge PR 29662
46e2d4447a [ci skip] Merge PR 29661 46e2d4447a [ci skip] Merge PR 29661
01ad9a87d5 [ci skip] Merge PR 29654 01ad9a87d5 [ci skip] Merge PR 29654
543741b864 [ci skip] Merge PR 29582 543741b864 [ci skip] Merge PR 29582
b57847baec Update gnuvid to 2.3 (#29657) b57847baec Update gnuvid to 2.3 (#29657)
6fe58002a6 [ci skip] Merge PR 29656 6fe58002a6 [ci skip] Merge PR 29656
51d39d12c9 Update mothur to 1.45.3. (#29648) 51d39d12c9 Update mothur to 1.45.3. (#29648)
b3b20187a2 [ci skip] Merge PR 29641 b3b20187a2 [ci skip] Merge PR 29641
cd72c9b0df [ci skip] Merge PR 29649 cd72c9b0df [ci skip] Merge PR 29649
f914b4c668 Clair3 version update to v0.1.5 (#29645) f914b4c668 Clair3 version update to v0.1.5 (#29645)
d65e364630 [ci skip] Merge PR 29594 d65e364630 [ci skip] Merge PR 29594
0cda28246e Update Meta.yaml (#29636) 0cda28246e Update Meta.yaml (#29636)
ee067084bc Update mosdepth to 0.3.2 (#29639) ee067084bc Update mosdepth to 0.3.2 (#29639)
48cef95d0a Update phispy to 4.2.19 (#29403) 48cef95d0a Update phispy to 4.2.19 (#29403)
9b8b34a9ff [ci skip] Merge PR 29629 9b8b34a9ff [ci skip] Merge PR 29629
1e1bb9694f [ci skip] Merge PR 29630 1e1bb9694f [ci skip] Merge PR 29630
bce65d59ac [ci skip] Merge PR 29524 bce65d59ac [ci skip] Merge PR 29524
81537fe92f [ci skip] Merge PR 29614 81537fe92f [ci skip] Merge PR 29614
2ab97905f7 [ci skip] Merge PR 29628 2ab97905f7 [ci skip] Merge PR 29628
f97da5b847 Metaplatanus (#29593) f97da5b847 Metaplatanus (#29593)
45c2295cb7 [ci skip] Merge PR 29627 45c2295cb7 [ci skip] Merge PR 29627
5a25fbd7b3 Update sourmash to 4.2.1 (#29622) 5a25fbd7b3 Update sourmash to 4.2.1 (#29622)
...
其中提交 WIP
是我尝试过的解决方法,而不是问题。
日志不停地往下走,我发现了 2624 个不同之处,例如这 3 个:
> 03f566bd3c 2nd try
> 1b1da3bfc8 Merge branch 'bioconda:master' into master
> 3c9a3fd0d1 updated tasmanian-mismatch
如果我打开 PR 是否需要处理这些差异?在打开 PR 之前如何与上游同步。
谢谢!
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。