From aba74f280e7d73d1ce91b2545eb25c9d62b34f85 Mon Sep 17 00:00:00 2001 From: Lee Cattarin Date: Wed, 14 Oct 2026 08:48:25 -0700 Subject: [PATCH] some tweaks to git post --- src/posts/2026/2026-01-07-intro-to-git.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/posts/2026/2026-01-07-intro-to-git.md b/src/posts/2026/2026-01-07-intro-to-git.md index f032bc57..53d623db 100644 --- a/src/posts/2026/2026-01-07-intro-to-git.md +++ b/src/posts/2026/2026-01-07-intro-to-git.md @@ -436,7 +436,7 @@ running `ssh-keygen` will take us through a series of prompts. Assuming we don't when you choose a passphrase, *write it down*. If you lose it, there is no recourse. You will have to generate a new SSH key. -after generation, we will have two files at the location specified by the tool (or the custom location we chose). Generally, that's the folder `.ssh` in our home directory. If we navigate to that directory (`cd $HOME/.ssh`) and look at the files (`ls`), we'll see files named `id_rsa` and `id_rsa.pub`. The one that ends with `.pub` is the *public* key. +after generation, we will have two files at the location specified by the tool (or the custom location we chose). Generally, that's the folder `.ssh` in our home directory. If we navigate to that directory (`cd $HOME/.ssh`) and look at the files (`ls`), we'll see files named `id_rsa` and `id_rsa.pub` (or maybe `id_ed25519` and `id_ed25519.pub` or something else). The one that ends with `.pub` is the *public* key. #### an alias... @@ -492,7 +492,7 @@ in order for all this to be useful, we need to tell Codeberg about our SSH key. ### `git push`, take two -we can now call `git push` again and again now without having to repeat our credentials every time. We can also call `git pull` for our private repositories. +whether we're using HTTPS or SSH, we can now call `git push` again and again now without having to repeat our credentials every time. We can also call `git pull` for our private repositories. ## summary