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

Aperta
  • Qualcosa non va?
#1,600 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
25/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
git, github, typescript
Ambito
devops, release

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
TypeScript
Stelle
1
Fork
1
Merge medio
11h 3m
PR unite (30g)
84

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di sequant-io/sequant

Tutte le issue di sequant-io/sequant

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.