Signing workflow #441
Open
Signing workflow #441
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
Kristy605
reviewed
Jan 18, 2023
|
Hi @Kristy605, and welcome 馃檭 The workflow on how to set up commit signing using Secretive SSH keys is explained better in #439: https://github.com/maxgoedjen/secretive/pull/439/files |
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.
afff88c implements the Git SSH signing setup.
It lacks the ability to automatically set the
user.signingkey-option, asIMO setting this option should happen in either
SecretDetailView.swiftorSecretListItemView.swift, but I'll open an issue to discuss this (see Secretive is Opinionated)2f2870d is just me trying to appease Markdownlint. On the plus side, the APP_CONFIG.md is now a little more colorful.