From c0ed918f867373df0768fadccbc5b2caede19fc9 Mon Sep 17 00:00:00 2001
From: CJ Yuan <cjyuan00@gmail.com>
Date: Mon, 19 May 2025 19:28:24 +0100
Subject: [PATCH 1/3] Create pull_request_template.md

---
 .github/pull_request_template.md | 35 ++++++++++++++++++++++++++++++++
 1 file changed, 35 insertions(+)
 create mode 100644 .github/pull_request_template.md

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 00000000..c3e0510b
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,35 @@
+<!--
+
+You must title your PR like this:
+
+REGION | COHORT_NAME | FIRST_NAME LAST_NAME | PROJ_NAME
+
+For example,
+
+  London | May-2025 | Carol Owen | Sprint-1
+
+-->
+
+## Learners, PR Template
+<!--
+  The purpose of the self-checklist is to help ensure the quality and completeness of a PR submission.
+
+  You must complete all the tasks in the self-checklist and tick the boxes for those you have finished.
+
+  You can tick a box by changing [ ] to [x] (with no spaces inside the brackets).
+-->
+
+Self checklist
+
+- [ ] I have titled my PR with REGION | COHORT_NAME | FIRST_NAME LAST_NAME | PROJ_NAME
+- [ ] My changes meet the requirements outlined in the `README.md` of this task
+
+## Changelist
+
+<!--
+  When you submit a PR, you're submitting changes you made to your own copy (fork) of the repository and requesting a review of those changes.
+  It is best practice to leave a brief description of the changes you have made.
+
+  You must replace "Briefly explain your PR." with a brief description of the changes you have made.
+-->
+Briefly explain your PR.

From e3056a6b2fbabd7a537143ab11c7f1375bb12741 Mon Sep 17 00:00:00 2001
From: CJ Yuan <cjyuan00@gmail.com>
Date: Mon, 19 May 2025 19:39:42 +0100
Subject: [PATCH 2/3] Add a "review not required" note

---
 README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 729cb32f..f6a309ea 100644
--- a/README.md
+++ b/README.md
@@ -26,11 +26,12 @@ To learn more about **pull requests** and how to create one, please use this gui
 
 9. Open a `Pull Request` to this repository
 
-## Finished Work
+## How to check your work?
+If you have correctly submitted your PR, you can find it in https://github.com/CodeYourFuture/GitHomeworkTest/pulls.
 
-When you've finished you should have a `pull request` that looks like this
+Your PR should look like this: https://github.com/CodeYourFuture/GitHomeworkTest/pull/692
 
-https://github.com/CodeYourFuture/GitHomeworkTest/pull/1
+**Please note that your PR will not undergo an official review, as none is required.** Most PRs at CodeYourFuture get reviewed, but this one is just for you to practice creating them.
 
 ## Asking for Help
 

From dcfa4bf4c6fa01d2d8d279c9160963b15fac281b Mon Sep 17 00:00:00 2001
From: CJ Yuan <cjyuan00@gmail.com>
Date: Sat, 17 Jan 2026 15:53:24 +0000
Subject: [PATCH 3/3] Update README with forking and cloning instructions

Added instructions for forking and cloning the repository.
---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index f6a309ea..b085079a 100644
--- a/README.md
+++ b/README.md
@@ -2,6 +2,8 @@
 
 To complete this homework you should use the Git workflow you've been learning this week.
 
+newly added
+
 1. Fork this repository to create a version where you are the owner
 2. Clone the fork to your local machine
 3. Open the local repository in VSCode