Open kaovilai opened 5 days ago
@kaovilai How about using prepare-commit-msg hook? By doing the following, the AI-generated message by oco will be set from the beginning when you commit with git. This way, you can use all git options in combination.
$ oco hook set // set prepare-commit-msg hook
$ git commit --signoff // in addition to the signoff message, the message generated by oco is set from the beginning (overwriting is also possible)
Sure if it would be documented as the way opencommit dev prefer to this issue.
Description
https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff
Suggested Solution
oco --signoff \<email>
if this takes too long we can alias.
Alternatives
set in some config file
or have a way to not have oco prompt for push
oco config set OCO_GITPUSH=false
.. then we can&& git commit --amend --signoff && git push --force
Additional Context
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/managing-the-commit-signoff-policy-for-your-repository#about-commit-signoffs
https://wiki.linuxfoundation.org/dco
For linux foundation, DCO is a requirement.