In this lesson, you will learn about the journey of a Pull Request. This is like following a story from beginning to end. You will make a simple drawing or write a short story about how a Pull Request goes from being made, to being checked, to finally being added to the main code. This will show that you understand the whole process.

For this lesson, your job is to explain how a Pull Request works from start to finish. There are no computer tests to run for this part. You just need to think about all the steps a Pull Request goes through.

Now, you will create your simple diagram or written summary. Think about these steps:

1. Making the PR: You create a Pull Request to show your new code.
2. Checking the PR: Other people look at your code and give you ideas or say if it's good.
3. Approving the PR: If everyone agrees the code is good, they say 'yes' to your Pull Request.
4. Adding the Code: Your new code is then added to the main game.

You can draw a simple picture with arrows, or write a short story using these steps to show how a Pull Request works.

You've explained the Pull Request journey! Now, look at your diagram or summary.

Ask yourself:

✅ Does it clearly show how a Pull Request goes from being made to being added to the main code? ✅ Does it include the steps of making, checking, approving, and adding the code?

If you answered yes to these questions, you did a great job!