What does this MR do?
It update the docs related to signing commits with GPG
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
GPG Key ID is missing without the --keyid-format arg:
gpg --list-secret-keys maxima_lubowitz@jones.ca
sec rsa4096 2017-09-13 [SC]
F105F034A9B4C2D7CDD999B9B8F3039BFCC6A7D2
uid [ultimate] Gregorio Roob <maxima_lubowitz@jones.ca>
ssb rsa4096 2017-09-13 [E]It's present only after adding the --keyid-format arg:
gpg --list-secret-keys --keyid-format LONG maxima_lubowitz@jones.ca
sec rsa4096/B8F3039BFCC6A7D2 2017-09-13 [SC]
F105F034A9B4C2D7CDD999B9B8F3039BFCC6A7D2
uid [ultimate] Gregorio Roob <maxima_lubowitz@jones.ca>
ssb rsa4096/8BE73A7633EEAE18 2017-09-13 [E]This is also used by GitHub in their docs
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if it does - rebase it please) -
Squashed related commits together