-
Notifications
You must be signed in to change notification settings - Fork 217
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
Save commit message #23
Labels
enhancement
New feature or request
Comments
Agreed, it’s useful for people signing commits and failing the GPG secret prompt. 😆 |
RianFuro
added a commit
to RianFuro/neogit
that referenced
this issue
Feb 28, 2021
Since the commit can fail for various reasons, we keep the commit message file after the user closes the buffer and only remove it after the commit was successful. Upon opening the commit buffer, we read the commit file's contents, if it exists, and present it as the suggested commit message
RianFuro
added a commit
to RianFuro/neogit
that referenced
this issue
Feb 28, 2021
Since the commit can fail for various reasons, we keep the commit message file after the user closes the buffer and only remove it after the commit was successful. Upon opening the commit buffer, we read the commit file's contents, if it exists, and present it as the suggested commit message
RianFuro
added a commit
to RianFuro/neogit
that referenced
this issue
Feb 28, 2021
Since the commit can fail for various reasons, we keep the commit message file after the user closes the buffer and only remove it after the commit was successful. Upon opening the commit buffer, we read the commit file's contents, if it exists, and present it as the suggested commit message
RianFuro
added a commit
to RianFuro/neogit
that referenced
this issue
Feb 28, 2021
Since the commit can fail for various reasons, we keep the commit message file after the user closes the buffer and only remove it after the commit was successful. Upon opening the commit buffer, we read the commit file's contents, if it exists, and present it as the suggested commit message
RianFuro
added a commit
to RianFuro/neogit
that referenced
this issue
Feb 28, 2021
Since the commit can fail for various reasons, we keep the commit message file after the user closes the buffer and only remove it after the commit was successful. Upon opening the commit buffer, we read the commit file's contents, if it exists, and present it as the suggested commit message
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When in a repo that uses git hooks, commit might not go through. Saving the commit message and reopening it if the last command didn't go through would be good. If it's stored in a file, not overriding the content of the file if it exists (only replacing the commented lines) would solve the issue.
The text was updated successfully, but these errors were encountered: