Resolve "Update the docs for GPG for gpg2 - [secret key not available]"
What does this MR do?
Update docs for gpg with gpg2.
Are there points in the code the reviewer needs to double check?
Nope
Why was this MR needed?
Update docs with gpg2 which comes installed on some systems and git still points to gpg.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together