Skip to content

Commit 6cabd6b

Browse files
author
github-actions
committed
Update to 3 in STEP and README.md
1 parent 941db4d commit 6cabd6b

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

.github/script/STEP

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

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ When you want to create a crosslink, start typing the title of an issue or pull
7878
TBD-step-2-notes.
7979
-->
8080

81-
<details id=2 open>
81+
<details id=2>
8282
<summary><h2>Step 2: Find a commit in history</h2></summary>
8383

8484
An important part of version control is the ability to look into the past. By using `git blame`, and finding the story behind a commit, we're able to do more than _blame_ people for code. We're able to see the story around why a commit was made. What is the associated pull request? Who approved the pull request? What tests were run on that commit before it was merged?
@@ -113,7 +113,7 @@ A SHA is a reference to a specific object. In this case, it's a reference to a c
113113
TBD-step-3-notes.
114114
-->
115115

116-
<details id=3>
116+
<details id=3 open>
117117
<summary><h2>Step 3: Fix a broken sidebar</h2></summary>
118118

119119
Thanks for finding that commit! We now know that the sidebar was indeed added, and it was done in that commit. Let's see if we can dig a little deeper to find out if any planning or conversation, using comments, occurred around this change.

0 commit comments

Comments
 (0)