Skip to main content
In this lesson we’ll explain the purpose of the primary pull request (PR) tabs on GitHub and how to use them effectively during code review. GitHub organizes PRs into distinct tabs—Conversation, Commits, Checks, and Files changed—so reviewers can quickly find the right context (discussion, history, automated results, or diffs) and make high-quality decisions. Understanding each tab helps streamline reviews, reduce back-and-forth, and improve merge confidence. The four PR tabs covered here:
  • Conversation
  • Commits
  • Checks
  • Files changed
Conversation tab The Conversation tab is the PR’s communication center. It contains the initial PR description, threaded comments, reviewer feedback, and chronological events (branch updates, reviewer assignments, CI/bot notifications). Use this tab to align on scope, technical direction, and acceptance criteria. When to use the Conversation tab:
  • Read the PR description to understand intent and scope.
  • Follow threaded discussions to track unresolved questions and decisions.
  • Review timeline events to see when and why the branch changed (rebases, force-pushes, merges).
  • Summarize outcomes or link to follow-up issues.
The image depicts a pull request discussion interface on GitHub, highlighting tabs for conversation, commits, and checks. It also explains that the discussion thread is a central place for PR discussions, including descriptions, comments, and feedback.
Commits tab The Commits tab shows a chronological, commit-by-commit history of changes on the branch. It helps reviewers follow the developer’s incremental thought process—useful for complex refactors or feature work split across multiple commits. Use this tab to:
  • Inspect individual commits for intent, scope, and descriptive messages.
  • Detect problematic commits that should be squashed, split, or amended.
  • Match a particular change to the author and timestamp for context.
  • Step through commits while reading diffs to see how the code evolved.
The image explains the purpose of pull request tabs, specifically the "Commits" tab, highlighting its role in showing granular history and progressive context in code changes. It includes a screenshot of a pull request with a specific focus on commits.
Checks tab The Checks tab is your automated gatekeeper: it aggregates CI build results, test outcomes, linters, and security scans. Before investing time in a manual review, check this tab to ensure programmatic gates have passed. Typical items shown in Checks:
  • CI status (build and test pass/fail).
  • Security and compliance reports (vulnerabilities, secrets scanning, static analysis).
  • Linter/style violations and coverage reports.
  • Links to logs and artifacts for troubleshooting.
A green checks summary usually indicates the repository’s automated requirements are satisfied and the PR is ready for focused human review.
The image explains the purpose of pull request tabs related to checks on GitHub, highlighting status reporting for tests and builds, and security & compliance for scan and linting results.
Files changed tab The Files changed tab is where the detailed technical review happens. It shows a unified diff across all modified files, lets you comment inline on specific lines, and provides suggested changes authors can apply directly. When reviewing files:
  • Verify changes are minimal and scoped to the issue or feature.
  • Leave precise, line-specific comments for clarity or suggested fixes.
  • Use the “suggested change” feature for small edits contributors can accept.
  • Confirm documentation and tests accompany behavior changes when applicable.
This tab is also where reviewers formally approve the PR, request changes, or resolve comments. After approvals and passing checks, follow your repository’s merge policy to complete the PR. Summary table Additional resources
Tip: Start reviews by checking the Checks tab to confirm automated tests and linters pass. Then use the Commits tab to understand the author’s intent and the Files changed tab to leave targeted, inline feedback. Use the Conversation tab to resolve discussions and document final decisions.

Watch Video