Repository navigation
docs: issue templates — structured bug form + explicit blank template - #1300
Conversation
|
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. |
|
解决ci失败问题 |
… explicit blank template (#1300)
b17b697 to
e8ec08b
Compare
📦 Built Package ArtifactBranch: Option A — Install from npm PR tag (recommended)npm install -g billion-context@pr-1300Each push to this PR publishes a new version under the Option B — Download artifact
tar xzf billion-context-pr1300.tgz
npm install -g packageInstall instructions are refreshed on each push. |
[bot] 🏷 CI 已修复并全绿。 一句话总结:CI 失败不是模板的问题,而是 PR #1298 的提交 CI 失败根因(已验证)
修复内容
关联发现:PR #1298 有同样的病(超出本 PR 范围,未动它)#1298 的 head 就是那个 |
…ient+version / OS / upstream) + explicit blank template
e8ec08b to
8982177
Compare
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):Optional fields: 压缩配置(yaml render)/ 日志片段 /
/acporacp_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).