Skip to content

Commit b221646

Browse files
committed
upgrade deps
1 parent 39a5e71 commit b221646

File tree

3 files changed

+252
-69
lines changed

3 files changed

+252
-69
lines changed

README.md

Lines changed: 6 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,8 @@ You are not allowed to collaborate during the sprint challenge.
1010

1111
## Project Setup
1212

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`.
1815

1916
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)
2017

@@ -38,24 +35,20 @@ Your finished project must include all of the following requirements (further in
3835

3936
**IMPORTANT Notes:**
4037

41-
- Execute tests locally by running `npm test`.
4238
- Do not exceed 2^8 rounds of hashing with `bcryptjs`.
4339
- If you use environment variables make sure to provide fallbacks in the code (e.g. `process.env.SECRET || "shh"`).
4440
- You are welcome to create additional files but **do not move or rename existing files** or folders.
4541
- Do not alter your `package.json` file except to install extra libraries. Do not update existing packages.
4642
- The database already has the `users` table, but if you run into issues, the migration is available.
4743
- 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.
5045

5146
## Submission format
5247

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.
5750
- [ ] 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.
5952

6053
## Interview Questions
6154

0 commit comments

Comments
 (0)