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

Merge queue squash commit fails required_signatures when a wrapped PR body line starts with 'committer '

Abierto
  • ¿Algo no está bien?
#7,279 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
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git, github, github-actions, shell
Área
ci-cd, devtools

Línea de trabajo

Start by inspecting the /source-control:pull-request body tooling and the pr-contract CI check mentioned in the issue. Reproduce the wrapping at 72 columns and check whether any wrapped body line starts with a Git commit header keyword. Done means the queue no longer creates an invalid signed squash commit for this case, with a check that catches the offending line before merge.

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

Descripción

needs-human

The merge queue removed #7225 twice with branch_protection_failure, even though its CI passed in the queue.

What happened

  • The queue's squash commit c2b54b0, committed by GitHub, shows verification.reason: invalid. The required_signatures rule (org ruleset signing, 17989003) then refuses it.
  • GitHub builds the squash message from the PR body and wraps it at about 72 columns. One wrapped line began committer identity set in the step env.
  • In the signed payload, the gpgsig block sits right after that body line, not after the real committer header. So the signing placed the signature after the first line starting committer .
  • The previous squash commit on main, 4a453b0, is valid.
  • Rewording the body so no wrapped line starts with committer fixed it.

Who acts and what they do

PR authors and the PR body tooling (/source-control:pull-request) should keep any line of the wrapped body from starting with a git header keyword, committer above all. One option is a ci-status pr-contract check that wraps the body at 72 columns and fails on ^(tree|parent|author|committer|gpgsig|encoding|mergetag) . That check would catch it before the queue does.

Evidence: gh api repos/melodic-software/claude-code-plugins/git/commits/c2b54b03e9c0bcacbf7367a2fa923d3ee308bcf9 --jq .verification

🤖 Generated with Claude Code

Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
8 h 25 min
PR fusionados (30 d)
944

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.