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

[FR]Sort tags and branches list before 64-revision cap so pruning keeps newest N refs

未关闭
#1,016 6 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@brendan-kellam 已经在做这个了。

开始于 2026年3月23日。

评估

这个 Issue 还没有评估数据。

描述

Feature

When tags and branches match many refs, Sourcebot truncates to 64 revisions using revisions.slice(0, 64) after listing tags via plain git.tags() / git tag ordering. That order is ref-name order, not recency. For many repos this is naturally oldest tags first. I am guessing this is the opposite of what many users want.

Git already supports explicit ordering (e.g. git tag --sort=-creatordate, --sort=-committerdate, --sort=-version:refname). This request is to apply an explicit sort before truncation. And ideally have that exposed in the config.

Relation to unlimited branches / tags

There is already ongoing work toward removing the 64 revision cap #461 and related PRs). That helps orgs that want a full ref index.

Even with unlimited or much higher limits, a lot of people will still want optionally capped index size and cost. A newest N tags/branches or newest by last commit date policy seems like the natural knob to pass in.

Might be worth adding that sort option and keeping a cap in that other branch.

Currently right now I get my oldest x tags while working on software that matches live code to its sourcebot index for that tag. Naturally I am missing all tags.

主要语言
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 摘要。