PR command publishes later PRs in the stack
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
Start by reproducing the behavior with git stack pr -p on the first branch of a stack, then compare it with the behavior when --all is passed. Trace the PR publishing command's stack traversal and verify whether later branches are only published or also have PRs created; done means -p handles only the requested branch while --all retains its broader behavior.
Written by the indexing model from the issue text.
Description
If you git stack pr -p on the first branch of a stack, it will also publish all of the PRs for later branches even though I didn't pass --all. It's possible that this also would create PRs for those later branches (I don't think so?). Need to investigate that as well.
- Dominant language
- Python
- Stars
- 17
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
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.
More from stevearc/gitstack
-
Slow on larger repos Open
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in stevearc/gitstack
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
use-agent-os/agent-os#3314 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
BasedHardware/omi#15662 · 1 comment ·
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
AiursoftWeb/AnduinOS-2#19 ·