{"id":15414722,"url":"https://github.com/tobysolutions/skills-review-pull-requests","last_synced_at":"2026-03-19T12:38:15.528Z","repository":{"id":236659415,"uuid":"637737690","full_name":"tobySolutions/skills-review-pull-requests","owner":"tobySolutions","description":"My clone repository","archived":false,"fork":false,"pushed_at":"2023-06-01T22:59:53.000Z","size":29,"stargazers_count":0,"open_issues_count":1,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-03-01T03:32:24.489Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"HTML","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/tobySolutions.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2023-05-08T09:58:17.000Z","updated_at":"2023-05-08T09:58:23.000Z","dependencies_parsed_at":"2024-04-28T05:39:17.401Z","dependency_job_id":"2ca35228-b03d-4f7d-b210-bf197a3b31e1","html_url":"https://github.com/tobySolutions/skills-review-pull-requests","commit_stats":null,"previous_names":["tobysolutions/skills-review-pull-requests"],"tags_count":0,"template":false,"template_full_name":"skills/review-pull-requests","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tobySolutions%2Fskills-review-pull-requests","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tobySolutions%2Fskills-review-pull-requests/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tobySolutions%2Fskills-review-pull-requests/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/tobySolutions%2Fskills-review-pull-requests/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/tobySolutions","download_url":"https://codeload.github.com/tobySolutions/skills-review-pull-requests/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":241366120,"owners_count":19951285,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-01T17:04:40.139Z","updated_at":"2026-02-10T00:03:30.791Z","avatar_url":"https://github.com/tobySolutions.png","language":"HTML","funding_links":[],"categories":[],"sub_categories":[],"readme":"\u003c!--\n  \u003c\u003c\u003c Author notes: Header of the course \u003e\u003e\u003e\n  Include a 1280×640 image, course title in sentence case, and a concise description in emphasis.\n  In your repository settings: enable template repository, add your 1280×640 social image, auto delete head branches.\n  Add your open source license, GitHub uses Creative Commons Attribution 4.0 International.\n--\u003e\n\n# Review pull requests\n\n_Collaborate and work together on GitHub._\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Start of the course \u003e\u003e\u003e\n  Include start button, a note about Actions minutes,\n  and tell the learner why they should take the course.\n  Each step should be wrapped in \u003cdetails\u003e/\u003csummary\u003e, with an `id` set.\n  The start \u003cdetails\u003e should have `open` as well.\n  Do not use quotes on the \u003cdetails\u003e tag attributes.\n--\u003e\n\n\u003cdetails id=0\u003e\n\u003csummary\u003e\u003ch2\u003eWelcome\u003c/h2\u003e\u003c/summary\u003e\n\nAll great projects start with collaboration. Pull requests are the foundation of teamwork on GitHub — and pull request reviews give you the ability to work together and discuss changes specific to a pull request by commenting, requesting changes, or approving.\n\n- **Who is this for**: Developers, new GitHub users, users new to Git, students, managers, teams.\n- **What you'll learn**: When and how to request a review; how to provide a review of someone else's pull request.\n- **What you'll build**: We'll be reviewing a pull request for a simple game.\n- **Prerequisites**: We assume you are familiar with creating branches, commits, and pull requests—you can learn this in our [Introduction to GitHub](https://github.com/skills/introduction-to-github) course.\n- **How long**: This course is five steps long and takes less than 30 minutes to complete.\n\n## How to start this course\n\n\u003c!-- For start course, run in JavaScript:\n'https://github.com/new?' + new URLSearchParams({\n  template_owner: 'skills',\n  template_name: 'review-pull-requests',\n  owner: '@me',\n  name: 'skills-review-pull-requests',\n  description: 'My clone repository',\n  visibility: 'public',\n}).toString()\n--\u003e\n\n[![start-course](https://user-images.githubusercontent.com/1221423/235727646-4a590299-ffe5-480d-8cd5-8194ea184546.svg)](https://github.com/new?template_owner=skills\u0026template_name=review-pull-requests\u0026owner=%40me\u0026name=skills-review-pull-requests\u0026description=My+clone+repository\u0026visibility=public)\n\n1. Right-click **Start course** and open the link in a new tab.\n2. In the new tab, most of the prompts will automatically fill in for you.\n   - For owner, choose your personal account or an organization to host the repository.\n   - We recommend creating a public repository, as private repositories will [use Actions minutes](https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions).\n   - Scroll down and click the **Create repository** button at the bottom of the form.\n3. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 1 \u003e\u003e\u003e\n  Choose 3-5 steps for your course.\n  The first step is always the hardest, so pick something easy!\n  Link to docs.github.com for further explanations.\n  Encourage users to open new tabs for steps!\n--\u003e\n\n\u003cdetails id=1\u003e\n\u003csummary\u003e\u003ch2\u003eStep 1: Open a pull request\u003c/h2\u003e\u003c/summary\u003e\n\n_Welcome to \"Review pull requests\"! :wave:_\n\nLet's get started by opening a pull request.\n\n**What is a pull request?**: Collaboration happens on a pull request. The pull request shows the changes in your branch to other people. This pull request is going to keep the changes you just made on your branch and propose applying them to the `main` branch.\n\n### :keyboard: Activity: Create a pull request\n\n1. Click on the **Pull requests** tab in your repository.\n2. Click **New pull request**.\n3. In the **base:** dropdown, make sure **main** is selected.\n4. Select the **compare:** dropdown, and click `update-game`.\n5. Click **Create pull request**.\n6. Enter a title for your pull request: `Update the game over message`.\n7. Enter a description for your pull request: `Update the game over message so people know how to play again!`\n8. Click **Create pull request**.\n\nNext, wait about 20 seconds for actions to run, then refresh this course's README (the one you're following instructions from) and a [GitHub Action](https://docs.github.com/en/actions) will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 2 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n  Historic note: this step combines the commend, approve, and needs changes steps from the previous version.\n--\u003e\n\n\u003cdetails id=2\u003e\n\u003csummary\u003e\u003ch2\u003eStep 2: Assign yourself\u003c/h2\u003e\u003c/summary\u003e\n\n_Great job opening that pull request! :wave:_\n\n**What is a _pull request review_?**: Reviewing a pull request is an opportunity to examine another contributor's changes and give them feedback. It's an awesome opportunity to learn more about how the project works and how others solve problems.\n\nThe best way to get a review is to ask for one. On GitHub, you can ask someone to review a pull request by assigning them as a reviewer or assignee. If you are not ready for review, consider [creating a draft pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) instead.\n\n### :keyboard: Activity: Assign yourself\n\n1. Open the pull request you just created.\n1. Under **Assignees** on the right side of the screen, add yourself.\n\nBecause you created the pull request, you can't assign yourself as a reviewer, but feel free to assign a friend as a reviewer instead to see how it works :smile:\n\nNext, wait about 20 seconds for actions to run, then refresh this course's README (the one you're following instructions from) and a [GitHub Action](https://docs.github.com/en/actions) will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 3 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n  Historic note: this step combines the commend, approve, and needs changes steps from the previous version.\n--\u003e\n\n\u003cdetails id=3\u003e\n\u003csummary\u003e\u003ch2\u003eStep 3: Leave a review\u003c/h2\u003e\u003c/summary\u003e\n\n_You assigned yourself! :tada:_\n\nPull request reviews ensure quality and maintain momentum of changes to your project.\n\n#### When reviewing a pull request:\n\n1. Review the _title_ and _body_ of the pull request, and possibly any associated issue, to understand the intended change.\n1. Review the [diff](https://docs.github.com/en/get-started/quickstart/github-glossary#diff), the comparison of the proposed code, in the context of the whole project.\n1. For most things, try out the proposed change. Check if the actual change matches the intention. Find the repository's [contributing guide](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors) to find out how to review the changes.\n\n#### In your review comments:\n\n- Identify potential issues, risks, and limitations.\n- Suggest changes and improvements.\n- Share awareness of upcoming changes that the pull request doesn't account for.\n- Ask questions to verify shared understanding.\n- Highlight what the author did well and should keep doing.\n- Prioritize the most important feedback.\n- Be concise _and_ provide meaningful detail.\n- Treat the pull request author with kindness and empathy.\n\nWhen an approval or request for changes is not yet needed, consider using **comments**. An **approval** lets the author know you believe the pull request is safe to merge. **Requesting changes** lets the author know you believe the pull request is not ready to merge.\n\n### :keyboard: Activity: Leave a review\n\n1. On the pull request, click **Files changed**.\n1. Click **Review changes**.\n1. Add a comment with your initial thoughts on the pull request.\n1. Select _comment_. You won't be able to _approve_ or _request changes_ to your own pull request.\n1. Click **Submit review**.\n\nNext, wait about 20 seconds for actions to run, then refresh this course's README (the one you're following instructions from) and a [GitHub Action](https://docs.github.com/en/actions) will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 4 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n--\u003e\n\n\u003cdetails id=4\u003e\n\u003csummary\u003e\u003ch2\u003eStep 4: Suggest changes\u003c/h2\u003e\u003c/summary\u003e\n\n_Nice work reviewing that pull request :sparkles:_\n\nNow that you have explored the different ways you can review a pull request it is time to learn how to use _suggest changes_.\n\n**What is _suggest changes_?**: This feature enables you to recommend a change to a pull request that the author can commit with the push of a button.\n\n### :keyboard: Activity: Suggest changes\n\n1. On the pull request, click **Files changed**.\n1. Find the `index.html` changes.\n1. Hover your cursor next to the line numbers on the left side of the page.\n1. Click the blue plus icon.\n1. After the comment form appears, click the **Add a suggestion** button. \u003cbr\u003e\n![add-a-suggestion-button](https://user-images.githubusercontent.com/97056108/184449714-61e8ee51-824a-48c1-9436-2dfd67f2c070.png)\n1. Edit the suggestion.\n1. Click **Add a single comment**.\n\nNext, wait about 20 seconds for actions to run, then refresh this course's README (the one you're following instructions from) and a [GitHub Action](https://docs.github.com/en/actions) will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 5 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n--\u003e\n\n\u003cdetails id=5\u003e\n\u003csummary\u003e\u003ch2\u003eStep 5: Apply suggested changes\u003c/h2\u003e\u003c/summary\u003e\n\n_Nicely done suggesting changes! :partying_face:_\n\nNow let's see how easy it is to [apply your suggestion](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request).\n\n### :keyboard: Activity: Apply suggested changes\n\n1. Click **Commit suggestion**.\n1. Type a commit message.\n1. Click **Commit changes**.\n\nNext, wait about 20 seconds for actions to run, then refresh this course's README (the one you're following instructions from) and a [GitHub Action](https://docs.github.com/en/actions) will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Step 6 \u003e\u003e\u003e\n  Start this step by acknowledging the previous step.\n  Define terms and link to docs.github.com.\n--\u003e\n\n\u003cdetails id=6\u003e\n\u003csummary\u003e\u003ch2\u003eStep 6: Merge your pull request\u003c/h2\u003e\u003c/summary\u003e\n\n_Almost there! :heart:_\n\nYou can now [merge](https://docs.github.com/en/get-started/quickstart/github-glossary#merge) your pull request!\n\n### :keyboard: Activity: Merge your pull request\n\n1. Click **Merge pull request**.\n1. Delete the branch `update-game` (optional).\n\nNext, wait about 20 seconds for actions to run, then refresh this course's README (the one you're following instructions from) and a [GitHub Action](https://docs.github.com/en/actions) will automatically close this step and open the next one.\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Finish \u003e\u003e\u003e\n  Review what we learned, ask for feedback, provide next steps.\n--\u003e\n\n\u003cdetails id=X open\u003e\n\u003csummary\u003e\u003ch2\u003eFinish\u003c/h2\u003e\u003c/summary\u003e\n\n_Congratulations friend, you've completed this course!_\n\n\u003cimg src=https://octodex.github.com/images/hula_loop_octodex03.gif alt=celebrate width=300 align=right\u003e\n\nAs you continue working on GitHub, remember that high quality reviews improve your projects. If you are new to a repository, inquire about what review practices they have so you can hit the ground running.\n\nHere's a recap of all the tasks you've accomplished in your repository:\n\n- You learned how to assign pull requests for review.\n- You left a review on a pull request.\n- You suggested changes to a pull request.\n- You applied suggested changes to a pull request.\n\n### What's next?\n\n- Try adding a [`CODEOWNERS`](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners) file to your project to automatically assign reviewers to pull requests.\n- We'd love to hear what you thought of this course [in our discussion board](https://github.com/skills/.github/discussions).\n- [Take another GitHub Skills course](https://github.com/skills).\n- [Read the GitHub Getting Started docs](https://docs.github.com/en/get-started).\n- To find projects to contribute to, check out [GitHub Explore](https://github.com/explore).\n\n\u003c/details\u003e\n\n\u003c!--\n  \u003c\u003c\u003c Author notes: Footer \u003e\u003e\u003e\n  Add a link to get support, GitHub status page, code of conduct, license link.\n--\u003e\n\n---\n\nGet help: [Post in our discussion board](https://github.com/skills/.github/discussions) \u0026bull; [Review the GitHub status page](https://www.githubstatus.com/)\n\n\u0026copy; 2022 GitHub \u0026bull; [Code of Conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) \u0026bull; [MIT License](https://gh.io/mit)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftobysolutions%2Fskills-review-pull-requests","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Ftobysolutions%2Fskills-review-pull-requests","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Ftobysolutions%2Fskills-review-pull-requests/lists"}