Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#7,218 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
markdown, shell
Área
tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
8 h 41 min
PR fusionados (30 d)
892

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.