Lab 1 (take home lab, 01/27/26)
Lab 2 (01/30/26)
Lab 3 (02/06/26)
Lab 4 (02/13/26)
Lab 5 (02/20/26)
Lab 6 (02/27/26)
Lab 7 (02/27/26)
cd ~/Gen711-811 git remote add upstream https://github.com/jthmiller/gen711-811 git fetch upstream
If you forked gen711-811, the easiest method to get the updates each week is to log in to your GitHub in a browser, navigate to your copy of the 'gen711-811' repo. If there are updates to be had, you should see 'update fork' button. This will bring the new files/changes to your GitHub repo, but not to your 'remote repo' of gen711-811 on RON. To pull the updates to your RON remote repo, open VScode, connect to RON (as above). Once you've connected to RON, go to 'File --> Open Folder'. Scroll down to and click 'gen711-811'. Click the bubble fork on the left. Near the 'Changes' meun, you should see '...'. If you click on it, you should see a 'fetch' option. Let me know if you see an error as a result.
HCGS youtube playlist for introduction to shell commands here
Taken from this repo
# H1
## H2
### H3
#### H4
##### H5
###### H6
Alternatively, for H1 and H2, an underline-ish style:
Alt-H1
======
Alt-H2
------
Alternatively, for H1 and H2, an underline-ish style:
Emphasis, aka italics, with *asterisks* or _underscores_.
Strong emphasis, aka bold, with **asterisks** or __underscores__.
Combined emphasis with **asterisks and _underscores_**.
Strikethrough uses two tildes. ~~Scratch this.~~
Emphasis, aka italics, with asterisks or underscores.
Strong emphasis, aka bold, with asterisks or underscores.
Combined emphasis with asterisks and underscores.
Strikethrough uses two tildes. Scratch this.
1. First ordered list item
2. Another item
⋅⋅⋅⋅* Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
⋅⋅⋅⋅1. Ordered sub-list
4. And another item.
⋅⋅⋅You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).
⋅⋅⋅To have a line break without a paragraph, you will need to use two trailing spaces.⋅⋅
⋅⋅⋅Note that this line is separate, but within the same paragraph.⋅⋅
⋅⋅⋅(This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)
* Unordered list can use asterisks
- Or minuses
+ Or pluses
- First ordered list item
- Another item ⋅⋅⋅⋅* Unordered sub-list.
- Actual numbers don't matter, just that it's a number ⋅⋅⋅⋅1. Ordered sub-list
- And another item.
⋅⋅⋅You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).
⋅⋅⋅To have a line break without a paragraph, you will need to use two trailing spaces.⋅⋅ ⋅⋅⋅Note that this line is separate, but within the same paragraph.⋅⋅ ⋅⋅⋅(This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)
- Unordered list can use asterisks
- Or minuses
- Or pluses
Here's our logo (hover to see the title text):
Inline-style:

Reference-style:
![alt text][logo]
[logo]: https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 2"
Here's our logo (hover to see the title text):
Inline-style:

Reference-style:
![alt text][logo]
[logo]: https://github.com/adam-p/markdown-here/raw/master/src/common/images/icon48.png "Logo Title Text 2"
Here's our logo (hover to see the title text):
Here's our logo (hover to see the title text):