You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+42Lines changed: 42 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -435,6 +435,28 @@ T("This is some output for a {{.CMDTYPE}} command", subs)
435
435
436
436
*NOTICE* goi18n/v2 has some newer features that can make this a bit easier to deal with, but I'm not sure they are currently supported, so procede with caution in you make use of them.
437
437
438
+
Commands that accept a list of options to display should have those subbed into the string, not hard coded.
Always a good idea to sign commits, even if it takes a bit to setup.
619
+
620
+
1. `git config --global commit.gpgsign true` Enabled signed commits
621
+
2. `gpg --full-generate-key` Create a GPG key to sign commits with (use your github email)
622
+
3. `git commit --message="THE MESSAGE"` is your normal commit, but should now be signed! You may be prompted for a password
623
+
4. `git log --show-signature` confirm its signed.
624
+
5. `gpg --output email.pgp --armor --export [email protected]` will export your PUBLIC key so you can upload it to github.
625
+
626
+
627
+
## Windows setup
628
+
629
+
In windows GPG pops up an annoying window for password prompting. Following [Using Command-Line Passphrase Input for GPG with Git](https://betakuang.medium.com/using-command-line-passphrase-input-for-gpg-with-git-for-windows-f78ae2c7cd2e) to be prompted on the CLI
0 commit comments