Skip to content

docs: issue templates — structured bug form + explicit blank template - #1300

Merged
ranxianglei merged 3 commits into
masterfrom
2026-09-25_issue-templates
Sep 26, 2026
Merged

ranxianglei merged 3 commits into
masterfrom
2026-09-25_issue-templates

Conversation

@ranxianglei

Copy link
Copy Markdown
Owner

Motivated by the #1195 experience (reproduction depends on reporter environment; the discriminating evidence — bili version, mode, client, OS, upstream window — was missing from the report and had to be asked for one comment at a time) and the owner's request.

What lands

.github/ISSUE_TEMPLATE/bug_report.yml — GitHub issue form (typed fields, six required):

Field Why it's required
问题描述 repro steps
bili 版本 two session-fork fixes (#1104/#1107/#1168) shipped inside 0.1.148 — "is it already fixed for you" is now question #1
使用方式 dropdown: 代理 / 启动器 / 插件 native / MITM / 其他 — plugin vs proxy mode changes the whole wire contract (AGENTS.md §6)
客户端及版本 free text, description explicitly asks to mark opencode v1 vs v2 (they diverge, #1082/#1108); pi/codex/dsh/kimi/claude + version
操作系统 incl. WSL2 marker (Windows-only defects are a recurring class, e.g. #1292)
上游与模型 provider + model + declared window — window-declaration-vs-real-limit is a known root-cause family (#1195 hypothesis A)

Optional fields: 压缩配置(yaml render)/ 日志片段 / /acp or acp_status 输出 — the three artifacts every compression investigation ends up asking for.

.github/ISSUE_TEMPLATE/blank.md — explicit free-form choice (frontmatter-only; kept as a first-class option per owner request, alongside GitHub's built-in blank).

Labels: bug form pre-labels bug. YAML validated (9 fields, 6 required).

Refs: #1195 (motivating case), #1148/#1102 (the fixes that made "which version" load-bearing).

@ranxianglei

Copy link
Copy Markdown
Owner Author

Switched both templates to English per review (open-source default audience): form labels, dropdown options, placeholders and descriptions all rewritten in English. Field set unchanged — 9 fields, 6 required (description / bili version / usage mode / client+version / OS / upstream), optional: compression config, log excerpt, /acp or acp_status output. The opencode v1 vs v2 marker and WSL2 marker survive in field descriptions. YAML re-validated.

@ranxianglei

Copy link
Copy Markdown
Owner Author

解决ci失败问题

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 收到,正在排查 PR #1300 的 CI 失败原因:先拉取分支 2026-09-25_issue-templates,再查该 head commit 的 check runs 定位失败项。稍后反馈结论与修复。

ranxianglei pushed a commit that referenced this pull request Sep 25, 2026
@ranxianglei
ranxianglei force-pushed the 2026-09-25_issue-templates branch from b17b697 to e8ec08b Compare September 25, 2026 05:22
@github-actions

github-actions Bot commented Sep 25, 2026 •

Copy link
Copy Markdown
Contributor

📦 Built Package Artifact

Branch: 2026-09-25_issue-templates (a802800)

Option A — Install from npm PR tag (recommended)

npm install -g billion-context@pr-1300

Each push to this PR publishes a new version under the pr-1300 npm tag.

Option B — Download artifact

  1. Download the artifact from the Actions run
  2. Extract the tarball and install:
tar xzf billion-context-pr1300.tgz
npm install -g package

Install instructions are refreshed on each push.

@ranxianglei

Copy link
Copy Markdown
Owner Author

🤖 Powered by ework · qwen3.8-27b

[bot] 🏷 CI 已修复并全绿。 一句话总结:CI 失败不是模板的问题,而是 PR #1298 的提交 533eba52 误混进了本分支(其代码依赖 acp-kernel 从未发布的两个符号,typecheck 挂掉连带全部下游 job 变红);我把分支在最新 master 上重建、只保留两个模板文件并 force-push,现在 10 项 CI 全绿,可以合并。

CI 失败根因(已验证)

修复内容

  • 将 2026-09-25_issue-templates 直接在当前 master(570a2ea7,v0.1.148)上重建为 2 个提交后 force-push(特性分支,非 master):
    1. a0a1cd9a docs: issue templates — structured bug form + explicit blank template(即 review 后的最终英文版内容,未改动)
    2. e8ec08be 顺手修的小渲染问题(独立标注提交,1 行):表单引导语里 Fields marked **\\*** 双转义星号会渲染成 \*,改为代码 span `*`
  • 与 master 的 diff 现在恰好 = 2 个新文件(+96 行),无其他任何改动;不碰代码/配置/版本,对运行时行为零影响。
  • 本地验证:YAML 解析通过;9 个字段、6 required(description / bili-version / mode dropdown / client / os / upstream)、3 optional(config render: yaml / logs / acp-state);预打标 bug;blank.md frontmatter 合法;opencode v1-vs-v2 与 WSL2 标记均保留在字段描述中。
  • CI(head e8ec08be):10/10 success —— build-artifact、test ubuntu-22/24、test windows-22/24、version-guard、hermetic registry e2e、real codex e2e、real pi e2e、codex CODEX_HOME overlay。PR 状态:open、mergeable clean、2 files changed。

关联发现:PR #1298 有同样的病(超出本 PR 范围,未动它)

#1298 的 head 就是那个 533eba52,它的 CI 正以相同错误全线变红。按跨仓规则,需要先发布含这两个导出的 acp-kernel、确认 npm 可见,再在 #1298 里 bump pin,否则它永远过不了 typecheck。该问题已有 #1294/#1298 线程可追踪,故未另开 issue;若希望单独立一个跟踪项,说一声我就提。

@ranxianglei
ranxianglei force-pushed the 2026-09-25_issue-templates branch from e8ec08b to 8982177 Compare September 25, 2026 05:34
@ranxianglei
ranxianglei merged commit c030b56 into master Sep 26, 2026
12 checks passed
@ranxianglei
ranxianglei deleted the 2026-09-25_issue-templates branch October 15, 2026 05:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant