Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

fix(source-control): changelog fragment writer duplicates headings and edits other plugins' fragments

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

维护者通常 1 天内回复

@melodic-automation-lanes 已经在做这个了。

开始于 2026年10月18日。

  • #8228 来自 @melodic-automation-lanes —— 未关闭

评估

难度
3/5
预计耗时
1-2 天
新手友好度
72/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
markdown, shell
领域
tooling

调研方向

Start with scripts/write-changelog-fragments.sh and inspect how it selects fragments, updates headings, and determines the bump level. Then read the existing tests or test setup for this script and add cases for repeated headings, upward-only bump changes, merge-base filtering, and an in-progress merge. Done means each case passes and merge runs write no fragments.

由索引模型根据 Issue 内容生成。

描述

priority: medium

The source-control commit skill's scripts/write-changelog-fragments.sh has two defects. Both were seen repeatedly on 2026-10-11 (#7204, #7208, and the #7150 branch).

  1. A duplicate heading on every releasing commit. A second releasing commit on a branch appends another ### Fixed (or ### Added/### Changed) heading to the branch's fragment instead of adding its entry under the existing heading. markdownlint MD024 then fails lint-repo, and someone has to merge the headings by hand.
  2. It writes into other plugins' fragments during a merge. When run during a merge of main, it appended the commit's entry to fragments that the merge had just brought in from other plugins (.changes/harness-ops/fix-7203-..., .changes/source-control/feat-check-affected-push-hook-... on #7208). The entries had to be removed by hand.

Fix

  • Add each entry under the matching existing heading, creating the heading only when it is absent, and raise the bump level only upward.
  • Only touch fragments this branch created: ones not present on the merge base. Write nothing during an in-progress merge.
  • Add a test for each case.
主要语言
Shell
星标
22
派生
2
平均合并
7 小时 8 分钟
30 天内合并 PR
874

环境准备

  • 没有 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 摘要。