Sign with GPG

[JCHacking]

I have several repositories with the rule to only allow signed commits.

I see that with mike even if I configure the GPG, the commit that it generates is not signed, so it is rejected by GitHub.

error: failed to push branch doc to origin:
  warning: not sending a push certificate since the receiving end does not support --signed push
  ***
  remote: - Commits must have verified signatures.
  remote:   Found 1 violation:
  ***

Is there any possibility of implementing it? Any advice on how to approach it if I end up implementing it myself in this tool?

[jimporter]

mike just uses git fast-import to generate commits, so it does whatever that Git subcommand does. Maybe that supports GPG-signing, and maybe not (the Git documentation isn't really clear about this). If Git doesn't support that, then you can always just amend the commit generated by mike to add a signature. Something like git checkout gh-pages && git commit --amend -S would probably do the trick.

[JCHacking]

Good idea! I hadn't thought of that

Maybe it could be implemented automatically in mike with the postcommit concept, to read if the commit.gpgsign signature property exists and if so do the amend?

EDIT:
It seems that work has started here, but I see that it is not merged or finished Git Sign Commit fast-import and fast-export
I understand then that it does not implement the fast-import commit signature, otherwise it would not have wanted to implement this.

[JCHacking]

In case anyone is interested, or is in the same need, the solution that I have applied was:

Previous code:

mike deploy --branch doc --push "${VERSION}"
mike set-default --branch doc --push "${VERSION}"

New code with the solution applied:

mike deploy --branch doc "${VERSION}"
(git checkout doc && git commit --amend --no-edit) || { git checkout -; exit 1; }; git checkout -
mike set-default --branch doc "${VERSION}"
(git checkout doc && git commit --amend --no-edit) || { git checkout -; exit 1; }; git checkout -
git push --set-upstream origin doc

This will make that after each change, an amend is made, for that I have to follow the steps:

• checkout doc branch
• amend
• checkout original branch/tag
• finally manually upload both changes, using upstream to create the branch in case it does not exist.
  In case of any failure, return to the original branch and exit with code 1.