GitHub App token fallback misses recent issues in large repositories
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 68/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- github, github-actions, typescript
调研方向
从 Github.matcher() 和 frog publish 使用的 listAll() 回退开始。跟踪带标签的查找、权限处理和分页行为，然后执行 issue 中列出的四个测试场景。完成的标准是：重复发布会对有标签和无标签的目标中的匹配报告及出现标记进行去重，同时涵盖大型仓库中的最新 issue。
由索引模型根据 Issue 内容生成。
描述
Expected Behavior
Repeated frog publish runs find an issue created by an earlier run when it has the configured friction label and identical report and occurrence markers.
This should work when an Action-only workflow passes a GitHub App installation token, as documented in Frog's Action-only instructions.
Current Behavior
With a GitHub App installation token, Github.matcher() can treat the repository as unlabelled even when the same token successfully creates an issue with the configured label.
The publish result then includes the repository in unlabelled. The fallback calls listAll(), which requests issues oldest-first and stops after 50 pages of 100. In a repository with more than 5,000 issues, it does not inspect recently created Frog issues. A later publish can therefore create another issue for the same report and occurrence markers.
Possible Solution
Build the label-filtered issue index regardless of repos.get().permissions.push. Reading issues by label does not require permission to apply that label.
Keep the permission result for warning whether labels are expected to stick. If the labelled lookup misses, scan the unlabelled fallback newest-first so its bounded lookup includes recent reports.
Tests should cover:
- a token whose repository response does not indicate push permission while a matching labelled issue exists;
- a recent matching issue outside the oldest 5,000 repository issues;
- a destination where labels cannot be applied and the unlabelled fallback is required;
- report and occurrence marker deduplication across these paths.
Minimal Reproducible Example
- Use Frog 1.1.0 with a GitHub App installation token in a repository containing more than 5,000 issues.
- Configure
issue-authorfor the App bot and publish one unlinked entry. - Confirm that the issue has the configured label while the publish result reports the destination as unlabelled.
- Run
frog publishagain before merging the generatedissue:link. - Observe a second issue with the same report and occurrence markers.
The workflow follows Frog's documented custom-token configuration: it passes the installation token as the action's token, sets issue-author to the App bot login, and uses the same login in the issue-event guard. actions/create-github-app-token inherits the installation permissions by default.
Context
This can repeatedly file the same friction entry while the generated frog/sync pull request waits to merge. Restricting workflow triggers reduces the window but does not make publishing idempotent.
- 主要语言
- TypeScript
- 星标
- 267
- 派生
- 11
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
wevm/frog 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 88/100
-
frog log rejects Windows repository roots可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
-
feat: allow local log entries to select an issue form可能已有人在做 @emmajam 于 72 天前认领。 未关闭
难度 4/5 3-5 天 新手友好度 55/100
相似的 Issue
-
bnv-manager-v2: accept_invite creates the Mailcow domain admin before the commit可能已有人在做 @myOmikron 今天认领。 未关闭bug ready-for-agent
难度 2/5 1-3 小时 新手友好度 82/100
-
platform:windows tool triaged wontfix
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
nicolettas-muggelbude/RechnungsFee#448 ·
维护者通常 1 天内回复
-
Android bug feature/error-tracking react-native team/error-tracking
难度 2/5 1-3 小时 新手友好度 72/100
PostHog/posthog-js#5310 · 1 条评论 ·
维护者通常 1 天内回复