You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-13Lines changed: 6 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,11 +10,8 @@ You are not allowed to collaborate during the sprint challenge.
10
10
11
11
## Project Setup
12
12
13
-
-[ ] Fork and clone the repo. Delete your old fork from Github first if you are repeating this Unit.
14
-
-[ ] Open the assignment in Canvas and click on the "Set up git" option.
15
-
-[ ] Follow instructions to set up Codegrade's Webhook and Deploy Key.
16
-
-[ ] Make a commit and push it to Github.
17
-
-[ ] Check to see that Codegrade has accepted your git submission.
13
+
-[ ] Run `npm install` to install your dependencies.
14
+
-[ ] Run tests locally executing `npm test`.
18
15
19
16
For a step-by-step on setting up Codegrade see [this guide.](https://www.notion.so/lambdaschool/Submitting-an-assignment-via-Code-Grade-A-Step-by-Step-Walkthrough-07bd65f5f8364e709ecb5064735ce374)
20
17
@@ -38,24 +35,20 @@ Your finished project must include all of the following requirements (further in
38
35
39
36
**IMPORTANT Notes:**
40
37
41
-
- Execute tests locally by running `npm test`.
42
38
- Do not exceed 2^8 rounds of hashing with `bcryptjs`.
43
39
- If you use environment variables make sure to provide fallbacks in the code (e.g. `process.env.SECRET || "shh"`).
44
40
- You are welcome to create additional files but **do not move or rename existing files** or folders.
45
41
- Do not alter your `package.json` file except to install extra libraries. Do not update existing packages.
46
42
- The database already has the `users` table, but if you run into issues, the migration is available.
47
43
- In your solution, it is essential that you follow best practices and produce clean and professional results.
48
-
- Schedule time to review, refine, and assess your work and perform basic professional polishing including spell-checking and grammar-checking on your work.
49
-
- It is better to submit a challenge that meets MVP than one that attempts too much and does not.
44
+
- Schedule time to review, refine, and assess your work and perform basic professional polishing.
50
45
51
46
## Submission format
52
47
53
-
-[ ] Submit via Codegrade by committing and pushing any new changes.
54
-
-[ ] Create a pull request to merge `<firstName-lastName>` branch into `main`.
55
-
-[ ] Please don't merge your own pull request and make sure **you are on your own repo**.
56
-
-[ ] Check Codegrade for automated feedback.
48
+
-[ ] Submit via Codegrade by pushing commits to your `<firstName-lastName>` branch on Github.
49
+
-[ ] Check Codegrade before the deadline to compare its results against your local tests.
57
50
-[ ] Check Codegrade on the days following the Sprint Challenge for reviewer feedback.
58
-
-[ ]Any changes pushed after the deadline will not receive any feedback.
51
+
-[ ]New commits will be evaluated by Codegrade if pushed _before_ the sprint challenge deadline.
0 commit comments