Allow Bors to sign commits #1
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This adds a new `committer.signing_key` entry to `bors.toml`. When specified, Bors will sign commits with `gpg`. The referenced secret key must be installed in the local gpg key store, making this patch unsuitable for public deployment. Future development could include adding a page to Bors's web UI to upload a private key for signing operations.
cassiemeharry
force-pushed
the
signed-commits
branch
from
75c6160 to
c6dbcce
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds a new
committer.signing_keyentry tobors.toml. When specified, Bors will sign commits withgpg. The referenced secret key must be installed in the local gpg key store, making this patch unsuitable for public deployment.Future development could include adding a page to Bors's web UI to upload a private key for signing operations.