No way to delete a stack locally whose branches are deleted
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 68/100
Research direction
Start at the gh stack unstack --local entry point and reproduce the failure after gh stack sync has pruned the stack branches. Trace how unstack handles missing local and remote branches, then verify that a stack with both kinds of branches deleted is removed without failing.
Written by the indexing model from the issue text.
Description
Context
Our repo has the "Delete head on merge" option, which makes it so that when merging a stack from the GitHub website, the feature branches get deleted also.
Locally, I also ran gh stack sync which prompted me to prune the branches.
The stack remained for some reason (I see there's a related bug), so I tried to unstack it locally since it no longer existed on remote.
Issue / Feature request
I expected that gh stack unstack --local would destroy the stack even if the branches do not exist but it failed.
To clean my local repo, I had to re-create the branches in the stack with the same names and then unstack succeeded.
Is it possible to have unstack in the case where both the local & remote branches no longer exist to consider them pruned, skip them, and not fail?
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 73
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
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.
More from github/gh-stack
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
feature request topic: cli - general
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
feature request topic: auto-merge
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug topic: docs
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NVIDIA/gpu-operator#2955 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
cisagov/vulnrichment#337 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100