Skip to content

Commit 6ddecfb

Browse files
Update to 4 in STEP and README.md
1 parent f0fe268 commit 6ddecfb

File tree

2 files changed

+23
-28
lines changed

2 files changed

+23
-28
lines changed

.github/steps/-step.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
3
1+
4

README.md

Lines changed: 22 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -14,53 +14,48 @@ _Organize ideas and collaborate using Markdown, a lightweight language for text
1414
</header>
1515

1616
<!--
17-
<<< Author notes: Step 3 >>>
17+
<<< Author notes: Step 4 >>>
1818
Start this step by acknowledging the previous step.
1919
Define terms and link to docs.github.com.
2020
-->
2121

22-
## Step 3: Add a code example
22+
## Step 4: Make a task list
2323

24-
_Great job adding an image to the file :tada:_
24+
_Great job adding a code example to the file :partying_face:_
2525

26-
Let's add some code blocks. Code blocks can render differently depending on the language.
26+
**What is a _task list_?** A task list creates checkboxes to check off. They're very useful for tracking issues and pull requests. If you include a task list in the body of an issue or pull request, you'll see a progress indicator in your issue list. The syntax for task lists is very specific. Be sure to include the spaces where required, or else they won't render.
2727

28-
### Example 1
28+
### Example
2929

30-
<pre>
3130
```
32-
$ git init
33-
Initialized empty Git repository in /Users/skills/Projects/recipe-repository/.git/
31+
- [x] List syntax is required
32+
- [x] This item is complete
33+
- [ ] This item is not complete
3434
```
35-
</pre>
3635

3736
#### How it looks
3837

39-
```
40-
$ git init
41-
Initialized empty Git repository in /Users/skills/Projects/recipe-repository/.git/
42-
```
38+
- [x] List syntax is required
39+
- [x] This item is complete
40+
- [ ] This item is not complete
4341

44-
### Example 2
42+
### :keyboard: Activity: Add a task list
4543

46-
<pre>
47-
``` javascript
48-
var myVar = "Hello, world!";
49-
```
50-
</pre>
44+
GitHub Actions went ahead and made a branch for you. So you'll need to add to the file we've created in the branch, and we will check your work as you work through this course!
5145

52-
#### How it looks
46+
1. Return to your pull request.
47+
1. Use Markdown to create a task list. Here is an example:
5348

54-
```javascript
55-
var myVar = "Hello, world!";
56-
```
49+
```md
50+
- [ ] Turn on GitHub Pages
51+
- [ ] Outline my portfolio
52+
- [ ] Introduce myself to the world
53+
```
5754

58-
### :keyboard: Activity: Adding a code example
55+
Remember, a task list starts with the syntax `- [ ]` and then the task list item. The formatting is specific!
5956

60-
1. As you did before, edit the file in this pull request.
61-
1. In the file, add the correct Markdown for a code example of your choice.
6257
1. Use the **Preview** tab to check your Markdown formatting.
63-
1. Commit your changes.
58+
1. Commit the changes to the file.
6459
1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
6560

6661
<footer>

0 commit comments

Comments
 (0)