Open IdanAdar opened 5 years ago
Does a manual git commit
in the command line (hit Ctrl+`) also produce the issue?
No. When using git commit
it worked.
@IdanAdar thanks for the report. I believe this is an issue with the embedded Git, and I suspect I need to patch it to address this properly.
What's happening is inside the git-sh-setup
that your pre-commit hook is failing on this command:
# Source git-sh-i18n for gettext support.
. "$(git --exec-path)/git-sh-i18n"
That's because the output of git --exec-path
isn't resolving correctly. I can verify this by running the command directly against that version of Git:
$ ./git --exec-path
//libexec/git-core
This works fine on the command line because Git is installed at a known location, but the embedded Git needs to be "aware" that it's embedded inside a .app
(or in a version-specific path on Windows).
Thanks @shiftkey. Hopefully it's an easy fix. I'd like to continue using the client and of course promote it internally...
@IdanAdar i'm going to move this into dugite-native
which is the project that needs to address this issue (there's not much the app itself can do aside from update the package once it's been fixed).
Thanks. Still hopeful for fast resolution.
Not sure how well it is going to work but I copied my git-secrets file and pasted into the "C:\Users\%username%\AppData\Local\GitHubDesktop\app-2.2.3\resources\app\git\usr\bin" it allowed me to commit like I did before installing git secrets I have not tested if it will prevent uploading secrets yet.
Not sure how well it is going to work but I copied my git-secrets file and pasted into the "C:\Users%username%\AppData\Local\GitHubDesktop\app-2.2.3\resources\app\git\usr\bin" it allowed me to commit like I did before installing git secrets I have not tested if it will prevent uploading secrets yet.
To expand on the above:
My company now requires the use of a detect-secrets tool and a pre-commit step. After following the instructions and attempting to push a commit, it failed with the following:
The log file shows:
I don't know if the problem is on the GitHub Desktop 1.5.2 beta 0 side, the pre-commit side, the Git side or the Python side. Any clues to resolve this will be much appreciated.