-
Notifications
You must be signed in to change notification settings - Fork 163
Commit not working on latest 2 releases #476
Comments
To be clear, the commit message file opens, you type your message, try to save the file, and then this message appears. Is that correct? |
Yep, exactly as you describe. After I type my commit message and close that window, that little red error notification pops up in the top right corner, and the |
Only trim the file if the verbose commit feature is enabled
I've created a branch (476) with what I suspect is the fix. If you don't mind cloning that and replacing your installation of the package with it to give it a shot that would be great. |
@akonwi sorry it took me a bit, this worked! |
@akonwi mind letting me know when it's pushed up or merged into the official release? for now i'm going to use this branch 👍 |
Merged and published 👍 |
awesome! many thanks. |
For some reason, and I noticed this only happens with the latest 2 releases, when I try and add a commit message, it fails with an error:
Error: ENOENT: no such file or directory, open '/Users/andrewmartin/code/drew-web/.git/COMMIT_EDITMSG'
It does successfully stage the file, just won't save the commit message, which is somewhat frustrating. It was working great for awhile too, that's the strange thing.
I'm currently on
5.15.0
and it's working fine, anything later than that and this error happens.The text was updated successfully, but these errors were encountered: