fix(source-control): pull-request ready pushes from the session cwd, not the PR worktree
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- Medio día
- Aptitud para principiantes
- 68/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- git, github, shell
- Área
- cli, developer-experience, tooling
Línea de trabajo
Start from the source-control pull-request ready skill and the push step that calls push-branch.sh. Trace how the cwd vs PR worktree is chosen, then pass an explicit worktree, branch, or PR-derived refspec so a different session cwd cannot push the wrong branch or print up-to-date. Add a test that runs the script from worktree A for a PR on worktree B and asserts B is pushed or the script exits non-zero.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
On 2026-10-04 a subagent ran /source-control:pull-request ready 6275 against the PR's worktree (/home/kyle/worktrees/melodic-software-claude-code-plugins-fix-wizard-write-env). The skill's push step (push-branch.sh) ran from the session's working directory, a different worktree, printed "Everything up-to-date", and pushed nothing. The merge-base commit only reached the PR because the agent noticed and pushed from the PR's worktree by hand.
A caller that trusts the script's success would flip a PR ready whose pushed head lacks the base merge, so CI and review run on the old head.
Expected
The push step pushes the branch of the PR being readied, from that PR's worktree (or with an explicit worktree path or refspec), and fails, rather than reporting "up-to-date", when the session's working directory is not on that branch.
Acceptance
push-branch.shtakes the target worktree or branch explicitly, or resolves it from the PR number, and never pushes the cwd's branch for a different PR.- A test runs the script from worktree A for a PR on worktree B and asserts B's branch is pushed, or the script exits non-zero.
- Lenguaje dominante
- Shell
- Estrellas
- 22
- Forks
- 2
- Merge medio
- 5 h 11 min
- PR fusionados (30 d)
- 838
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de melodic-software/claude-code-plugins
-
good first issue needs-triage priority: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
melodic-software/claude-code-plugins#6631 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
melodic-software/claude-code-plugins#6547 ·
Los mantenedores suelen responder en 1 día
-
needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
melodic-software/claude-code-plugins#6535 ·
Los mantenedores suelen responder en 1 día
-
test_comment_census.py: SccArgv flag-shaped-filename test errors on Windows (#!/bin/sh scc shim)Abiertogood first issue needs-triage priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
melodic-software/claude-code-plugins#6532 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
good first issue needs-triage priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
melodic-software/claude-code-plugins#6390 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de melodic-software/claude-code-plugins
Issues similares
-
status:needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
enhancement good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Sorogate/example-consumer#14 ·
-
github_actions good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
alunduil/alunduil-chezmoi#874 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
alunduil/zellij-claude-pair#53 ·
Los mantenedores suelen responder en 1 día