Decide whether to create the org Priority issue field

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

维护者通常 1 天内回复

@kyle-sexton 已经在做这个了。

开始于 2026年11月8日。

评估

这个 Issue 还没有评估数据。

描述

needs-triage priority: medium status: needs-decision

Decision

Create an org-level Priority issue field (single select) to replace the four priority: labels on issues, or keep the labels until issue fields leave public preview.

Context

  • GitHub ships Priority as a default issue field and recommends a single-select field for a preset list such as priority (Managing issue fields; Best practices for Projects, read 2026-11-08).
  • Issue fields are still documented as public preview.
  • Creating a field is an owner step in org settings, recorded in github-iac's expected-org-security drift record, as for Size, Complexity and Uncertainty (github-iac ADR 0016).
  • Option names follow the org rule for field options: lowercase kebab-case (owner decision Q18, 2026-11-08).

Done when

  • The owner creates the field (options critical, high, medium, low) and its ids are added to the github-iac drift record, or the owner chooses to keep the labels; either answer is recorded on this issue, which then closes.

Closing this issue unblocks #14074.

主要语言
Shell
星标
22
派生
2
平均合并
56 分钟
30 天内合并 PR
959

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

melodic-software/claude-code-plugins 的其他 Issue

查看 melodic-software/claude-code-plugins 的全部 Issue

相似的 Issue

更多 Shell/Bash Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。