Kr Younger před 6 roky
rodič
revize
e891ffffd9
2 změnil soubory, kde provedl 11 přidání a 5 odebrání
  1. 8
    2
      README.TXT
  2. 3
    3
      README.md

+ 8
- 2
README.TXT Zobrazit soubor

@@ -1,3 +1,9 @@
1
+FIRST SATURDAY
2
+==============
3
+
4
+Lab Brief
5
+---------
6
+
1 7
 The objective of this lab is to give you an opportunity to think through IF statements
2 8
 and LOOPS (WHILE, DO WHILE, and FOR).
3 9
 
@@ -12,6 +18,6 @@ Run All Tests on the class until you pass them all. For each of the loop methods
12 18
 you need to put the code about w = w + 1; inside of the loops. It lets the test know how
13 19
 many iterations of the loop your code did. This data is used to make sure you passed the tests.
14 20
 
15
-You may not change ANY existing test methods.
21
+You may not change ANY existing test methods. You get extra credit(!) for each test you add.
16 22
 
17
-Pass all the tests with your code.
23
+Be sure to pass all the tests with your code.

+ 3
- 3
README.md Zobrazit soubor

@@ -2,13 +2,13 @@
2 2
 
3 3
 First weekend lab. Overall idea is to read the code, read the tests, and then write some code to pass all the tests.
4 4
 
5
-**Be sure to Fork this repo, and `git clone` your own forked copy of this code.**
5
+**Be sure to Fork this repo into your account and `git clone` your own forked copy of this code in a terminal.**
6 6
 
7 7
 Be sure to commit all your changes multiple times as you're working on the lab.
8 8
 
9
-`git commit -m "checkpointing my work"` should so. But change the message to meaningful to the work you're saving.
9
+`git commit -m "checkpointing my work"` should do, be sure to change the message to something meaningful to the work you're saving.
10 10
 
11
-When you are finished, and are passing all the tests, be sure to do a final commit and then do a Pull Request so we can review your work.
11
+When you are finished, and are passing all the tests, be sure to do a final `git commit` and then do a `Pull Request` so we can review your work.
12 12
 
13 13
 
14 14