-
Notifications
You must be signed in to change notification settings - Fork 338
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
3.2.0 #412
3.2.0 #412
Conversation
* fix(prepare-commit-msg-hook): update error handling to provide clearer instructions for setting API keys and improve user guidance * build
@matscube thank you for your help, gonna publish soon. a review would be much appreciated. tests pass and i tested in 10 times locally, but if you see a concern — pls lmk |
@di-sukharev |
@matscube deployed, please update and lmk if it works for you, there are some tricky migrations to the config happening as you can see in the code. i've deleted a lot of redundant config vars and made it simpler to support |
@di-sukharev When I ran the
After running the migration, I ran
Also, the migration caused the API_KEY (OCO_OPENAI_API_KEY) setting to disappear, so I set OCO_API_KEY again. When I ran the
By migration, the following line will be automatically set in the global configuration file, but it seems that an error will occur if it is
If you comment out the line of It seems that an error occurs when By commenting out Some users might get in trouble. |
i see, preparing the patch |
@matscube hmm.. i dont see this behaviour. for me this is my config before migrations:
this is the config after migrations were applied:
|
i reproduced the behaviour. thank you |
will be fixed here #414 |
merged #413 |
I confirmed that it works properly. Thank you! |
No description provided.