Bump nokogiri from 1.11.4 to 1.12.5

[ZhangZhouhe]

Bumps nokogiri from 1.11.4 to 1.12.5.

• Release notes
• Changelog
• Commits

---

updated-dependencies:

• dependency-name: nokogiri
  dependency-type: indirect
  ...

Signed-off-by: dependabot[bot] support@github.com

[github-learning-lab]

I was expecting your file to be named _posts/0000-01-02-ZhangZhouhe.md.

Let's edit this pull request to fix both of these issues.

⌨️ Activity: Fixing the file name in your pull request

1. Click the Files Changed tab in this pull request.
2. Verify that the only file edited is named _posts/0000-01-02-ZhangZhouhe.md.
3. If the file is improperly named, or not in a proper location, use the edit function to correct it.
4. Above the contents of the file, select all text in the field that contains the filename and delete it.
5. Continue pressing your backspace key to also delete any directory names that exist.
6. Type the proper filename:

   _posts/0000-01-02-ZhangZhouhe.md

7. Scroll to the bottom and enter a commit message and commit in the Commit Changes section.

Note: You can find directions on how to move files while editing in our documentation.

If you would like assistance troubleshooting the issue you are encountering, create a post on the GitHub Community board. You might also want to search for your issue to see if other people have resolved it in the past.

---

I'll respond below when I detect a commit on this branch.

[github-learning-lab]

Step 7: Respond to a review

Your pull request is looking great!

Let’s add some content to your file. Replace line 5 of your file with a quotation or meme and witty caption. Remember: Markdown is supported.

⌨️ Activity: Change your file

1. Open the file _posts/0000-01-02-ZhangZhouhe.md.
2. Replace line 5 of the file with something new.
3. Stage your new changes. As a reminder, you can do this in the Source Control view, click the + symbol next to the file.
4. Commit your changes. You can do this in the Source Control view, enter a commit message in the text field and press Ctrl+Enter on Windows or Command ⌘+Enter on macOS.
5. Push your edits to GitHub. In the Source Control view, click on the ellipsis (...), and select Push.

Note : Can't find the button to edit the file? It may look like a pencil, or it may look like three dots.

---

I'll respond when I detect a commit on this branch.

[github-learning-lab]

Step 7: Respond to a review

Your pull request is looking great!

Let’s add some content to your file. Replace line 5 of your file with a quotation or meme and witty caption. Remember: Markdown is supported.

⌨️ Activity: Change your file

1. Open the file _posts/0000-01-02-ZhangZhouhe.md.
2. Replace line 5 of the file with something new.
3. Stage your new changes. As a reminder, you can do this in the Source Control view, click the + symbol next to the file.
4. Commit your changes. You can do this in the Source Control view, enter a commit message in the text field and press Ctrl+Enter on Windows or Command ⌘+Enter on macOS.
5. Push your edits to GitHub. In the Source Control view, click on the ellipsis (...), and select Push.

Note : Can't find the button to edit the file? It may look like a pencil, or it may look like three dots.

---

I'll respond when I detect a commit on this branch.

[github-learning-lab]

Step 8: Merge your pull request

Nicely done @ZhangZhouhe! ✨

You successfully created a pull request, and it has passed all of the tests. You can now merge your pull request.

⌨️ Activity: Merge the pull request

1. Click Merge pull request

2. Click Confirm merge

3. Once your branch has been merged, you don't need it anymore. Click Delete branch.

---

I'll respond when this pull request is merged.