Update draft PRs?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 569
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm wondering if there is a way to update draft PRs with this tool. Let's say I have a stack of 3 commits and run stack-pr submit --draft. It will create 3 local branches and 3 draft PR's. If I then make some changes to those three commits and run stack-pr submit --draft, I now see it creates 3 new local branches (total 6 now) and 3 new draft PRs (total 6 now). From the README, it seems like the second submit command should update the existing PR's. How do I ensure stack-pr keeps local branch to PR mapping for draft PR's? I'm also wondering why new branches get created on the second submit command?
Another piece of feedback is that if the above scenario happens and the user ends up with duplicate commits in the stack/branches, the user experience is very disorienting.
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 with the README's description of stack-pr submit --draft, then reproduce the three-commit workflow described in the issue. Trace how the command records local branch-to-PR mappings across a second submission. Done means updating the existing draft PRs without creating duplicate local branches, PRs, or commits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100