chore(repo): automatically delete head branches is off, so merged branches pile up
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 60/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, github-actions
- Domain
- devops
Research direction
Start by confirming the current state with gh api repos/flisk-sh/analytics --jq .delete_branch_on_merge; the payload already shows it returns false. The fix itself is a repo setting change (gh repo edit --delete-branch-on-merge) that requires admin rights, so a newcomer will likely need a maintainer to run it. For the code half, add a small check under .github/workflows/ that reads that field and fails when false. Done when the flag is true, merged branches are pruned, and the workflow passes.
Written by the indexing model from the issue text.
Description
Problem
flisk-sh/analytics has "Automatically delete head branches" turned off. Every merged pull request leaves its branch behind, so the branch list fills with stale branches that contributors then have to sort through (and that look like unfinished work).
Repro:
gh api repos/flisk-sh/analytics --jq .delete_branch_on_merge
# false
Root Cause Analysis
The repo setting was left at the GitHub default (off). It is a one-click repo setting, not a code change.
TDD Fix Plan
- RED: Add a small org-settings check (script or workflow) that fails when
delete_branch_on_mergeis false.
GREEN: Enable "Automatically delete head branches" in the repo settings (gh repo edit --delete-branch-on-merge).
REFACTOR: None expected.
Acceptance Criteria
-
delete_branch_on_mergeis true - Existing merged branches are cleaned up
- All new tests pass
- Existing tests still pass
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 2
- Avg merge
- 1h 33m
- Merged PRs (30d)
- 7
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from flisk-sh/analytics
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests
Difficulty 1/5 1-3 hours Newbie friendliness 84/100
All issues in flisk-sh/analytics
Similar issues
-
chore cloudflare-workers consistency d1 difficulty: easy documentation dx enhancement good first issue help wanted hygiene javascript maintenance priority: P3 seo
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
MattiaPARRINELLO/backstage#70 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
untemps/svelte-palette#298 ·