markormesher / markormesher/tedium
Prune merged branches
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 0
- Forks
- 0
- Avg merge
- 8h 54m
- Merged PRs (30d)
- 9
Description
// copied from original private repo
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue only identifies pruning merged branches and provides no files, tests, workflow, or branch list. Start by inspecting the repository's current Git branches and contribution guidance; completion would need a clearly defined set of obsolete merged branches and confirmation that the requested pruning is finished.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100