Bug: crashes when PR was merged on GH, but rebasing to `main` wasn't done
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 569
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
If the PR was merged using GH UI, and the user tries to run stack-pr export without doing rebase manually first, they'll get a crash. Ideally a tool should be smart enough to suggest running rebase to the user in the error message instead of throwing a stack trace.
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 at the stack-pr export command and reproduce the crash after a GitHub-merged PR has not been rebased onto main. Trace the resulting error path and make the failure explain that rebasing is required, with a direct suggestion to run it; done means the stack trace is replaced by that actionable message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, python
- Domain
- cli, developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100