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
Below those, let's add the prerequisite skills you determined earlier for your lesson.
74
+
This time, instead of committing directly to the `main` branch - we will save our changes on another branch and then do a pull request to merge them to `main` that will allow us to review and spot any issues.
74
75
75
76
## Proposing Changes with Pull Requests
76
77
@@ -133,13 +134,6 @@ Since a more in-depth discussion of pull request reviews is included in the GitH
133
134
134
135
:::::::::::::::::::::::::::::::::::::::::::::::
135
136
136
-
Once the changes have been merged and your lesson site rebuilds, check how prerequisites block appears on your lesson's home page.
alt="Lesson prerequisite fenced div structural block as rendered in a Web page by the Workbench"
141
-
}
142
-
143
137
You will have an opportunity to practice this pull request workflow in a moment.
144
138
145
139
We just added the prequisites as a bullet point list in `index.md`, but the Workbench provides a special formatted block for lesson prerequisites, so they appear visually distinct on the page.
@@ -160,6 +154,12 @@ Finally, end your fenced div with a closing tag consisting of at least 3 colons
160
154
and we will explore most of them in this episode.
161
155
:::
162
156
157
+
A screenshot below provides an example of how prerequisites block appears in a webpage.
0 commit comments