bug: Skipping because githook is not run on commit about gptcommit HOT 8 CLOSED

$ RUST_LOG=trace git commit -a
2023-01-20T04:26:30.577Z DEBUG [gptcommit] Args { action: PrepareCommitMsg(PrepareCommitMsgArgs { commit_msg_file: ".git/COMMIT_EDITMSG", commit_source: Template, commit_sha: Some(""), git_diff_content: None }) }
🤖 Skipping gptcommit because githook is not run on commit
hint: Waiting for your editor to close the file...

Looking at commit_source: Template it seems you might have a commit template
set. Can you try removing the git config --local commit.template and see if the issue goes away.

Because the githook detected the user is supplying their own template, we make sure not to overwrite it with GPT

from gptcommit.

Thanks for the feedback! Can you try running the git commit command with the RUST_LOG envvar set to trace?

RUST_LOG=trace git commit ...

That might get give us a bit more context into what is going on

from gptcommit.

Thanks for your reply!

These are the outputs:

$ RUST_LOG=trace git commit -a
2023-01-20T04:26:30.577Z DEBUG [gptcommit] Args { action: PrepareCommitMsg(PrepareCommitMsgArgs { commit_msg_file: ".git/COMMIT_EDITMSG", commit_source: Template, commit_sha: Some(""), git_diff_content: None }) }
🤖 Skipping gptcommit because githook is not run on commit
hint: Waiting for your editor to close the file...

from gptcommit.

I have the same problem.

➤  git status
On branch foobar
Changes to be committed:
  (use "git restore --staged <file>..." to unstage)
        new file:   test

➤  RUST_LOG=trace git commit        
🤖 Skipping gptcommit because githook is not run on commit

from gptcommit.

$ RUST_LOG=trace git commit -a
2023-01-20T04:26:30.577Z DEBUG [gptcommit] Args { action: PrepareCommitMsg(PrepareCommitMsgArgs { commit_msg_file: ".git/COMMIT_EDITMSG", commit_source: Template, commit_sha: Some(""), git_diff_content: None }) }
🤖 Skipping gptcommit because githook is not run on commit
hint: Waiting for your editor to close the file...

Looking at commit_source: Template it seems you might have a commit template set. Can you try removing the git config --local commit.template and see if the issue goes away.

Because the githook detected the user is supplying their own template, we make sure not to overwrite it with GPT

Thanks! It is working perfectly now! Very cool! I'd prefer if there is a way, maybe with flag, to switch between using GPT and local/global commit template. Or perhaps, a wrap over git commit -a with custom flag to overwrite the local/global template. Anyway, thanks a lot for your help!

from gptcommit.

It's great that it works!

I think you can now close the ticket, but it would be an added bonus to update the README file with a section on "frequent problems". What do you think?

from gptcommit.

Good point, I've updated the readme.

from gptcommit.

from gptcommit.