This repository was archived by the owner on Apr 30, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
[Backlog Discovery] feat(backlog): backlog-pr-issue-auto-labeling #95
Open
bestony
wants to merge
2
commits into
main
Choose a base branch
from
backlog/20260221055525-backlog-pr-issue-auto-labeling-backlog-
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| --- | ||
| source: backlog-discovery | ||
| dedupe_key: backlog-pr-issue-auto-labeling | ||
| priority: P2 | ||
| generated_at: 2026-02-21T05:53:53Z | ||
| status: TODO | ||
| --- | ||
|
|
||
| <!-- backlog-dedupe-key:backlog-pr-issue-auto-labeling --> | ||
|
|
||
| # Requirement: 为自驱生成的 Issue/PR 增加自动标签与优先级同步 | ||
|
|
||
| ## 1. Requirement Summary | ||
| - Backlog Discovery 与 Product Designer 等流程会自动创建 Issue/PR,但当前仓库缺少统一的标签与优先级映射机制,导致维护者无法快速筛选高优先级项或按类型分流,需求评审与执行排期效率降低。 | ||
|
|
||
| ## 2. Target Users | ||
| - 仓库维护者 | ||
| - 产品负责人 | ||
| - 自动化值班人员 | ||
|
|
||
| ## 3. Core Scenarios | ||
| - Backlog Discovery 自动创建 PR 后没有 priority/type 标签,维护者难以在 PR 列表中快速区分 P1/P2。 | ||
| - Product Designer 自动创建的需求 Issue 未标注来源类型与优先级,导致与人工 Issue 混杂,难以聚合跟踪。 | ||
| - 需要在 GitHub 界面或 Projects 中按优先级/类型过滤自驱产出的工作项,但缺少可用的标签体系。 | ||
|
|
||
| ## 4. User Problems | ||
| - Backlog Discovery 与 Product Designer 等流程会自动创建 Issue/PR,但当前仓库缺少统一的标签与优先级映射机制,导致维护者无法快速筛选高优先级项或按类型分流,需求评审与执行排期效率降低。 | ||
|
|
||
| ## 5. External Research Evidence | ||
| 1. GitHub Docs - Managing labels | ||
| - URL: https://docs.github.com/articles/editing-a-label | ||
| - 摘要: GitHub 官方文档说明可用 labels 来分类与管理 issues、pull requests,并支持创建、应用与维护标签体系。 | ||
| 2. GitHub Docs - REST API endpoints for labels | ||
| - URL: https://docs.github.com/rest/issues/labels | ||
| - 摘要: GitHub 提供 labels 的 REST API,可用于自动化创建、查询与更新 Issue/PR 标签。 | ||
| 3. GitHub Actions - actions/labeler | ||
| - URL: https://github.com/actions/labeler | ||
| - 摘要: actions/labeler 提供基于配置规则自动为 PR 添加标签的能力,体现社区对自动标签分流的需求。 | ||
|
|
||
| ## 6. Proposed Solution Hypothesis | ||
| - 新增 label 规范与自动化:在 Backlog Discovery / Product / Engineer 工作流中调用 GitHub API 或 labeler action,根据候选 priority 与来源类型自动打标。 | ||
| - 先收敛最小可用标签集(priority + type),明确默认开关策略(默认开启或需显式 opt-in),再逐步扩展。 | ||
| - 上线前补充仓库内证据:采样当前 PR/Issue 分流耗时或误判率,作为基线以验证效果。 | ||
|
|
||
| ## 7. Priority & Impact | ||
| - Priority: P2 | ||
| - Impact: 提升自驱产出需求的可见性与筛选效率,减少维护者在 PR/Issue 列表中的人工分流成本。 | ||
|
|
||
| ## 8. Acceptance Criteria | ||
| 1. 定义并维护一套最小可用标签体系(例如 priority:P0~P3、type:backlog/type:plan),并在 workflow 中自动校验或创建缺失标签。 | ||
| 2. 明确标签同步开关的默认策略(默认开启或 opt-in),并支持按工作流配置覆盖。 | ||
| 3. 当 Backlog Discovery 创建 PR 时,自动按候选项 priority 与类型映射添加标签,并在 PR body/summary 中写入已应用标签。 | ||
| 4. 当 Product Designer/Engineer 创建或更新 Issue/PR 时,自动同步或更新 priority/type 标签,且支持配置开关。 | ||
| 5. 上线前记录至少一项仓库内基线指标(例如分流耗时或误判率),用于验证自动标签的改进效果。 | ||
|
|
||
| ## 9. Metadata | ||
| - generated_at: 2026-02-21T05:53:53Z | ||
| - dedupe_key: backlog-pr-issue-auto-labeling | ||
| - english_desc: backlog-pr-issue-auto-labeling | ||
| - source_workflow: Backlog Discovery | ||
| - source_repository: bestony/self | ||
| - source_run_id: 22251460467 | ||
| - source_run_attempt: 1 | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The content of '4. User Problems' appears to be a direct duplicate of '1. Requirement Summary'. Consider if this section adds unique value or if it can be integrated into the summary to avoid redundancy.