-
Notifications
You must be signed in to change notification settings - Fork 273
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
Git write-back method and gpg-signed commits #427
Comments
Any chance that the changes from the commit that referenced this issue will be ported upstream? |
same issue, is there any solution?
|
This issue should already be resolved by #710 . From the error above, it looks like the gpg executable is not available. |
we have the same errors. gpg executable is missing in the image of updater, shouldn't it be part of it? |
This issue ( |
Is your feature request related to a problem? Please describe.
We use
git
write-back method, but our repository has branch protection rules, which require all commits tomain
branch to be signed with a gpg key. It looks like there is partial support for passing gpg key id to thegit commit
command here, but I can not find a way to configure bothCommitOptions.SigningKey
andCommitOptions.SignOff
options.Describe the solution you'd like
Support configuring these setting via
--git-commit-signing-key
and--git-commit-sign-off
cli args andGIT_COMMIT_SIGNING_KEY
andGIT_COMMIT_SIGN_OFF
env vars hereDescribe alternatives you've considered
Disable
require signed commits
requirement inmain
branch protection rules.The text was updated successfully, but these errors were encountered: