Add my slide

[yukon39]

Add my slide

[github-learning-lab]

Good pull requests have a body description that tells other contributors about the change you're suggesting, so they understand the context.

Let's edit this pull request to add a body description.

⌨️ Activity: Fixing your pull request

1. The first comment on your pull request will have the default text of No description provided. Click on the ... icon located at the top right corner of the comment box, then click on Edit to make an edit
2. Add a description of the changes you've made in the comment box. Feel free to add a description of what you’ve accomplished so far. As a reminder, you have: created a branch, created a file and made a commit, and opened a pull request
3. Click the green Update comment button at the bottom right of the comment box when done

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 when I detect this pull request's body has been edited.

[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-yukon39.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 @yukon39! ✨

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.

[github-learning-lab]

Nice work

Congratulations @yukon39, you've completed this course!

What went well

Now, you have your slide deck deployed here and you've gone through the GitHub Flow.

Before I say good-bye, here's a recap of all the tasks you've accomplished in your repository:

• You learned about issues, pull requests, and the structure of a GitHub repository
• You learned about branching
• You created a commit
• You viewed and responded to pull request reviews
• You edited an existing file
• You enabled GitHub Pages
• You made your first contribution! 🎉

Give us feedback

We'd love to hear what you thought of this course. Please share your feedback in this brief survey.

What's next?

We hope this course helped you feel more comfortable using GitHub. Remember: You’re always welcome to repeat course topics if you’d like additional practice. If you’re ready to build on your new skills, here are some ideas.

Contribute to a project

To find projects to contribute to through trending topics and curated collections, check out GitHub Explore.

Keep learning

Here are some suggestions for future courses you can take:

• GitHub Pages: Continue learning about GitHub Pages, which we touched on in this course.
• Communicating using Markdown: We used a little Markdown in this course, but if you want to learn all about this ✨ syntax, take the course!

What will you learn next?