aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Change 8: Moved the pseudocode to cst116-lab0-Pearse, as it would make more ↵HEADmainTim Pearse2022-10-052-31/+39
| | | | sense there.
* Change 7: Change 10 over the two gits. Hooray!Tim Pearse2022-10-051-0/+2
|
* Change 6: Moved the pseudocode to the checklist.txtTim Pearse2022-10-052-9/+9
|
* Change 5: Adding Pseudocode to the main file & adding checklist.txt Done ↵Tim Pearse2022-10-012-0/+15
| | | | | | | with this repository? Next Step: Review the Lab0 prep work, if necessary.
* Change 4: Uploading a text fileTim Pearse2022-10-011-0/+3
| | | | | Next Step : Write a flowchart and/or pseudo-code for this project. Put it into a file: include this file in your GitHub project. Either include this in “run” file from Step 11 or put it in a separate file with a name that starts similarly to the other files (CST116-Lab0-<lastname>) and ends with “-flowchart” or “-pseudo-code". This file also might be something other than a text file (in order to hold the flowchart.
* Change 3: Commiting because it's cool and the steps want me to do it hereTim Pearse2022-10-011-1/+1
| | | | | Next Step : Copy the output from the run of your program to a text file in your project. Give the text file the same name as your project (except for the extension).
* Change 2: Attempting to force GitHub to work.Tim Pearse2022-10-011-2/+9
| | | | | Next Step : Add a cout statement that lets the world know who you are and what your GitHub is. Be sure to include your GitHub name and an endl (no /n).
* Change 1, added comment details and using linesTim Pearse2022-10-011-0/+363
| | | | | Next Step: Add a cout statement that lets the world know who you are and what your GitHub is. Be sure to include your GitHub name and an endl (no /n).
* Setting up GitHub Classroom Feedbackgithub-classroom[bot]2022-10-010-0/+0
|
* GitHub Classroom Feedbackfeedbackgithub-classroom[bot]2022-10-011-0/+0
|
* Initial commitgithub-classroom[bot]2022-10-016-0/+214