docs: explicitly recommend SSH over HTTPS and add GitHub documentation link

bhouston · bhouston · commit 312f7392403f · 2025-03-22T12:35:26.000Z
diff --git a/packages/docs/docs/usage/github-action.md b/packages/docs/docs/usage/github-action.md
@@ -160,6 +160,8 @@ This clearly identifies commits made automatically by MyCoder.
 
 ### SSH Authentication
 
+While SSH authentication is generally recommended over HTTPS for most Git operations due to its security benefits, in automated environments like GitHub Actions, special considerations apply:
+
 When using GitHub Actions with SSH authentication:
 
 1. **Avoid SSH Keys with Passphrases**: For automated environments like GitHub Actions, use SSH keys without passphrases or use alternative authentication methods.
diff --git a/packages/docs/docs/usage/github-mode.md b/packages/docs/docs/usage/github-mode.md
@@ -142,6 +142,10 @@ If your team uses a complex GitHub workflow (e.g., with code owners, required re
 
 ### SSH Passphrase Best Practices
 
+MyCoder recommends using SSH authentication over HTTPS whenever possible, as SSH provides better security and doesn't require entering username/password credentials for each operation. However, if you use SSH keys with passphrases, proper configuration is necessary to prevent interruptions during automated operations.
+
+For detailed instructions, see [GitHub's official documentation on connecting with SSH](https://docs.github.com/en/authentication/connecting-to-github-with-ssh).
+
 When using GitHub mode with SSH authentication, it's important to properly manage SSH key passphrases to ensure automation works smoothly:
 
 1. **Use SSH Agent**: Configure ssh-agent to remember your passphrase, so you don't need to enter it repeatedly:
