Skip to content

Commit e66a501

Browse files
authored
Shape up prework (learn-co-curriculum#10)
* update readme for new sequencing * update gh workflow to remove prework flag
1 parent 7f96847 commit e66a501

File tree

2 files changed

+4
-21
lines changed

2 files changed

+4
-21
lines changed

.github/workflows/canvas-sync-html-prework.yml renamed to .github/workflows/canvas-sync-html.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
name: Sync with Canvas Pre-Work that Contains HTML
1+
name: Sync with Canvas HTML
22

33
on:
44
push:
@@ -25,7 +25,7 @@ jobs:
2525

2626
# Secret stored in learn-co-curriculum Settings/Secrets
2727
- name: Sync from .canvas file
28-
run: github-to-canvas -a -lr --forkable --prework --contains-html
28+
run: github-to-canvas -a -lr --forkable --contains-html
2929
env:
3030
CANVAS_API_KEY: ${{ secrets.CANVAS_API_KEY }}
3131
CANVAS_API_PATH: ${{ secrets.CANVAS_API_PATH }}

README.md

Lines changed: 2 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,7 @@ we've learned.
1414

1515
If you haven't already, fork and clone this lab into your local environment.
1616
Navigate into its directory in the terminal, then run `code .` to open the files
17-
in Visual Studio Code. Finally, run `npm install` to install the lab's
18-
dependencies.
17+
in Visual Studio Code.
1918

2019
## Instructions
2120

@@ -56,23 +55,7 @@ prone to bugs.
5655

5756
Remember the workflow:
5857

59-
1. Run the tests using `npm test`.
58+
1. Run the tests using `learn test`.
6059
2. Read the errors; vocalize what they're asking you to do.
6160
3. Write code; repeat steps 1 and 2 often until a test passes.
6261
4. Repeat as needed for the remaining tests.
63-
64-
## Saving Your Work Remotely
65-
66-
Currently, the work you've done on this assignment is only on your local
67-
machine. To preserve your solution on your GitHub fork, you will need to stage the
68-
changes you've made, commit them, and push the commit up to GitHub. Use
69-
the following commands to do this:
70-
71-
```console
72-
$ git add .
73-
$ git commit -m "Completed assignment"
74-
$ git push
75-
```
76-
77-
If you visit your fork on GitHub, you should now see that _you've_ made the most
78-
recent commit, and your code will be present in the files.

0 commit comments

Comments
 (0)