From b90d65abc156655b82770d139f37df40922299f0 Mon Sep 17 00:00:00 2001 From: github-actions Date: Fri, 23 Sep 2022 17:17:31 +0000 Subject: [PATCH] Update to 3 in STEP and README.md --- .github/script/STEP | 2 +- README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/script/STEP b/.github/script/STEP index 0cfbf08..00750ed 100644 --- a/.github/script/STEP +++ b/.github/script/STEP @@ -1 +1 @@ -2 +3 diff --git a/README.md b/README.md index 569ad70..7b2c28c 100644 --- a/README.md +++ b/README.md @@ -79,7 +79,7 @@ When you want to create a crosslink, start typing the title of an issue or pull TBD-step-2-notes. --> -
+

Step 2: Find a commit in history

 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? @@ -115,7 +115,7 @@ A SHA is a reference to a specific object. In this case, it's a reference to a c TBD-step-3-notes. --> -
+

Step 3: Fix a broken sidebar

 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.