Skip to content

Commit 013b694

Browse files
committed
better header levels
1 parent 6ea9d64 commit 013b694

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

git_cli.qmd

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -49,11 +49,11 @@ Here [`nano`](https://www.nano-editor.org) is used as example; you can choose mo
4949
Problem with any of those steps? Check out Jenny Brian [Happy git trouble shooting section](http://happygitwithr.com/troubleshooting.html){target="_blank"}
5050

5151

52-
### GitHub credentials
52+
## GitHub credentials
5353

5454
Normally if you have already used GitHub tokens your Operating System (Windows, MacOSX, ...) should have cached the necessary credentials to log in to your GitHub account (necessary to be able to push (write) content to the remote repository).
5555

56-
#### Setting up your GitHub Token
56+
### Setting up your GitHub Token
5757

5858
You can find the latest guidelines on how to setup your personal GitHub token **[here](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic)**
5959

@@ -78,7 +78,7 @@ Copy your token to your clipboard and then push to GitHub from the command line
7878

7979
Only once it has worked and that your token as been cached by your OS password manager you can close the GitHub webpage displaying your token value.
8080

81-
#### Setting up your SSH key
81+
### Setting up your SSH key
8282

8383
Another option is to set up the method that is commonly used by many different services to authenticate access on the command line. This method is called Secure Shell Protocol (SSH). SSH is a cryptographic network protocol that allows secure communication between computers using an otherwise insecure network.
8484

@@ -95,11 +95,11 @@ ls -al ~/.ssh
9595
Your output is going to look a little different depending on whether or not SSH has ever been set up on the computer you are using.
9696

9797

98-
##### Already set up:
98+
#### Already set up:
9999

100100
If SSH has been set up on the computer you're using, the public and private key pairs will be listed. The file names are either `id_ed25519`/`id_ed25519.pub` or `id_rsa`/`id_rsa.pub` depending on how the key pairs were set up.
101101

102-
##### Not Set up:
102+
#### Not Set up:
103103

104104
```bash
105105
ls: cannot access '/Users/brunj7/.ssh': No such file or directory

0 commit comments

Comments
 (0)