Land No Longer Deletes Remote Branch(es)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 569
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Version: 0.1.3
stack-pr generates remote branches in the form <user>/stack/# when you submit a stack. In 7cbd8ab it was asserted that Github deletes remote branches automatically. This only seems to be true if Automatically delete head branches setting is configured on the project. This does not seem to be a default. At present, stack-pr will leave these intermediate stack branches behind on the remote. stack-pr should query this setting if possible, and err on the side of removing resources (refs) it creates.
Contributor 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.
Research direction
Start by tracing how stack-pr creates and cleans up the remote /stack/# branches, then inspect the GitHub API surface for the project's automatic head-branch deletion setting. Done means intermediate refs created by stack-pr no longer remain on the remote, with the setting handled when possible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100