Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

FR: allow informing zoekt about `fetch --force`

未关闭
#33 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
git
领域
devops

调研方向

Start with the issue's git fetch failure example and investigate how sourcebot handles fetches and communicates repository state to Zoekt. No source file, test, or entry point is named. Done would require a decided way to support force-fetch behavior and verification that tags stay aligned with upstream.

由索引模型根据 Issue 内容生成。

描述

I would suspect there are a non-trivial number of repos that do force pushes, including overwriting tags:

2024/10/05 17:34:27 command [git --git-dir /data/.sourcebot/repos/github.com/JetBrains/intellij-community.git fetch origin --prune] failed: exit status 1
 ! [rejected]                  idea/191.7141.44     -> idea/191.7141.44  (would clobber existing tag)

In those scenarios, what sourcebot believes is the tag will not square up with the upstream's idea of the tag

I actually checked their issue tracker and surprisingly there doesn't seem to be an issue for influencing that behavior. So in that way, it's great you have a fork

If you want me to try and open the issue with them, let me know

主要语言
TypeScript
星标
3.9k
派生
374
平均合并
21 小时 18 分钟
30 天内合并 PR
39

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

sourcebot-dev/sourcebot 的其他 Issue

查看 sourcebot-dev/sourcebot 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。