Lesson 8 - Review and merge
Inspect, review, and merge the new work with GitHub tools in VS Code.
In this lesson, you will:
- commit the new work and create a pull request from Source Control.
- request a Copilot code review.
- address feedback and failing checks with GitHub MCP.
- merge the pull request.
Inspect, review, and merge
Copilot Free does not include Copilot code review for pull requests. Use Copilot Student or a paid Copilot plan that includes code review. An organization can also enable paid code review on GitHub.com for members without a Copilot license, but this does not grant IDE code review access. See Copilot code review availability.
If you do not have access, skip the Copilot review request in step 4. Review the diff yourself or ask a teammate to review it, then continue with the remaining steps, addressing any human review feedback and retesting before merging.
- Open Source Control to inspect the changed files and diff before you create anything.
- Commit the new work, using the sparkle button to write the message again.
- Select the Create Pull Request button that appears in Source Control. Copilot drafts the title and description from your commits, so you get a better pull request than asking for one from scratch.
- Request a Copilot code review while you create the pull request, from the GitHub view in VS Code, or on GitHub.
- Ask Copilot, with GitHub MCP, to inspect the pull request, resolve merge conflicts, address review comments, and investigate failing CI checks.
- Retest in the integrated browser, review every proposed change, and update the branch.
- When checks and review are complete, ask the agent to merge, or merge from the GitHub integration.
You can always ask Copilot to do this in chat instead. The Source Control path is worth learning first because it writes the commit and pull request text for you from what actually changed.
Summary and next steps
You reviewed and merged a pull request without leaving VS Code. Continue to Lesson 9: Hand the next idea to a cloud session.