Skip to content
Snippets Groups Projects
Verified Commit f8f4ae2a authored by Owen Graham's avatar Owen Graham
Browse files

Put screenshots in block quotes

parent 503de7e6
No related branches found
No related tags found
No related merge requests found
......@@ -222,7 +222,7 @@ git remote add origin https://gitlab.ssec.wisc.edu/YOUR_USERNAME/tut.git
git push -u origin main
```
![I get prompted to enter my login info while pushing][upload-push]
> ![I get prompted to enter my login info while pushing][upload-push]
You're all done!
Go find your repo at
......@@ -295,7 +295,7 @@ For this branch, put a couple fortunes into a file called `fortunes`.
(echo 'Beware of Bigfoot!'; echo; echo 'Tomorrow, you can be anywhere.') > fortunes
```
![I run "fortune" and put what it says into "fortunes"][branch-fortune]
> ![I run "fortune" and put what it says into "fortunes"][branch-fortune]
Stage and commit your fortunes.
......@@ -316,7 +316,7 @@ git merge fortune
git log
```
![I run "git switch" and "fortunes" disappears][branch-switch]
> ![I run "git switch" and "fortunes" disappears][branch-switch]
Checking `git log`, you can see that both branches now have the newest
commit from `fortune`.
......@@ -445,7 +445,7 @@ Look for `id_rsa.pub` or `id_ed25519.pub` in `~/.ssh/`.
ls ~/.ssh
```
![I find "id_ed25519.pub" in my ".ssh" folder][ssh-ls]
> ![I find "id_ed25519.pub" in my ".ssh" folder][ssh-ls]
If it's not there, run either of the following commands to make a key
pair:
......@@ -456,7 +456,7 @@ ssh-keygen -t ed25519
ssh-keygen -t rsa -b 4096
```
![I run "ssh-keygen"][ssh-keygen]
> ![I run "ssh-keygen"][ssh-keygen]
Now copy your public key and paste it into
<https://gitlab.ssec.wisc.edu/-/profile/keys>.
......@@ -468,9 +468,9 @@ cat ~/.ssh/id_ed25519.pub
cat ~/.ssh/id_rsa.pub
```
![I "cat" my public key file][ssh-cat]
![I paste my public key to a GitLab settings page][ssh-gitlab-pasted]
> ![I "cat" my public key file][ssh-cat]
>
> ![I paste my public key to a GitLab settings page][ssh-gitlab-pasted]
To start using SSH, make sure to change the protocol of your Git
remotes!
......@@ -485,7 +485,7 @@ git fetch
If you want a shiny "verified" marker on your commits, you should sign
them with a GPG key.
![The "verified" marker on one of my commits on GitLab][gpg-verified]
> ![The "verified" marker on one of my commits on GitLab][gpg-verified]
I'm not writing a guide for this one.
Try [GitLab's guide][gpg-guide].
......
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please to comment