[Bug]: Commit action changes staging before message generation succeeds
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 23k
- Forks
- 5.9k
- Avg merge
- 11h 14m
- Merged PRs (30d)
- 357
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
- Have staged and untracked changes.
- Make commit-message generation fail, such as by using a signed-out provider.
- Click Commit.
Expected behavior
No commit is created and the existing staging is unchanged.
Actual behavior
The commit flow runs git reset / git add -A before generating the message. If generation fails, the index stays changed.
Impact
Medium
Version or commit
main @ 2d156a83b
Environment
Any Git repository; provider failure is required to trigger the unsafe exit path.
Workaround
Restore the intended staging manually before the next commit.
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 in apps/server and trace the Commit action through the path that runs git reset and git add -A before message generation; reproduce with staged and untracked changes plus a signed-out provider. Done means a generation failure leaves the existing staging unchanged and creates no commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- backend, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100