`gh stack submit` does not save PR descriptions and titles if it fails
Open
bug
topic: cli - submit
- Dominant language
- Go
- Stars
- 1.5k
- Forks
- 70
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
When `gh stack submit` fails (like due to a poor internet connection, GitHub downtime, or a git hook #346), it forgets all the edits made on the PR screen, and the user has to redo everything next time.
Contributor guide
Research direction
Start at the gh stack submit command and reproduce a failed submission, such as with a poor connection, GitHub downtime, or the git hook from issue #346. Trace how edits made on the PR screen are handled when submission fails. Done means titles and descriptions remain available on the next attempt instead of needing to be re-entered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100