New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Killing the lint script still causes unstaged changes to be lost #1311
Comments
If there isn't a good way of ameliorating this, is there some means of asking |
Also when I was about to commit a commit with 200 + files and tens of thousands of changes |
lint-staged --no-stash |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
There was a previous issue: #583 which framed the experience I just had, but I'm running
[email protected]
— I was making a commit and realized I had skipped something and muscle memory kicked in and I hitCtrl+C
whilelint-staged
was in the middle of running the "Cleaning up temporary files..." step.This resulted in all my work being stashed but I didn't have a good means of introspecting where it went (and so I had to sort
.git/objects
by date and figure out the correct hash).I was able to overcome this problem, but it seems like the original issue wasn't solved (?)
Steps to reproduce
I believe this happened because I hit
Ctrl+C
whilelint-staged
was in the middle of running the "Cleaning up temporary files..." step, but I am not certain.Debug Logs
Environment
v18.15.0
lint-staged
:13.0.3
The text was updated successfully, but these errors were encountered: