Ctrl-C loses commits
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 569
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Pressing Ctrl-C in the middle of stacked-pr export loses commits & data. Ideally it should be more careful, save a checkpoint, and restore that on any interruption.
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 reproducing Ctrl-C during stacked-pr export and trace the export flow that handles interruption. Done means an interrupted export preserves a checkpoint and can restore it without losing commits or data; the payload names no files or tests to run.
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
- 35/100