Could we clean up the remote base, head, and orig branches after landing?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1k
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
I'm not sure if I'm using this tool correctly, but there are many leftover branches to remove after using ghstack.
https://github.com/takahirom/arbigent/branches/active
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
Start by reproducing the ghstack workflow described in the issue and inspect the remote base, head, and orig branches shown in the linked branches page. Determine which branches remain after landing and define completion as safely removing the leftover branches without affecting the landed stack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100