docs: clarify binary GPG validation #14832
Merged
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.
Let users know that warnings on "untrusted signature" don't mean a failed GPG validation.
This additional hint is targeted at novice users; people who know pgp well enough will understand gpg's output anyway.
If we'd instead aim to remove the warning (by adding a command to set the trustlevel for gitea's key) most people would blindly trust the docs, defeating the purpose of that gpg warning.
ref #14817