chore(repo): prune the 149 merged remote branches and turn on `delete_branch_on_merge` after one verifying PR

Abierto
  • ¿Algo no está bien?
#1,600 0 comentarios 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
4/5
Tiempo estimado
1-2 días
Aptitud para principiantes
25/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
git, github, typescript
Área
devops, release

Línea de trabajo

Read founding doc §6 D-4.1 under docs/internal/graph-2026-10-ergonomics/ and inspect scripts/dev/cleanup-worktree.sh. First verify the proposed setting with one merged PR whose branch is checked out in a worktree, then confirm cleanup removes the worktree entry. Done when the transcript and branch decisions for all 13 branches without PRs are recorded, merged PR branches are absent remotely, and delete_branch_on_merge is true.

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

Descripción

Problem

164 non-main remote branches on 2026-10-26; 149 match a merged PR's head by name (git branch --merged sees only 5 because merges are squashed), 127 have no commit in 30 days, 13 have no PR at all. The repo has delete_branch_on_merge: false. The reason it was never flipped is two memories about merges destroying worktrees, but scripts/dev/cleanup-worktree.sh already deletes the remote branch only when the PR is MERGED and tolerates the branch being gone (git push origin --delete … || true), and both recorded incidents were caused by gh pr merge --delete-branch run from inside a worktree or by uncommitted edits in a worktree whose PR merged, not by GitHub deleting the head branch. Founding doc §6 D-4.1 (docs/internal/graph-2026-10-ergonomics/).

Acceptance Criteria

  • AC-1: One PR is merged with delete_branch_on_merge on while its branch is checked out in a worktree, and cleanup-worktree.sh <branch> then completes without error and leaves git worktree list without the entry. Evidence: the command transcript pasted on this issue
  • AC-2: Merged-PR branches are gone from the remote. Evidence: gh pr list --state merged --limit 300 --json headRefName --jq '.[].headRefName' | sort -u | xargs -I{} git ls-remote --heads origin {} | wc -l | tr -d ' ' → 0
  • AC-3: The setting is on. Evidence: gh api repos/sequant-io/sequant --jq .delete_branch_on_merge → true
  • AC-4: The 13 branches with no PR are listed on this issue with a keep/delete decision each before any is deleted. Evidence: a comment on this issue listing them

Non-Goals

  • Deleting any branch with an open PR.
  • Changing cleanup-worktree.sh.
Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
10 h 59 min
PR fusionados (30 d)
86

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 sequant-io/sequant

Todos los issues de sequant-io/sequant

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.