Use a GitHub suggested change when you can specify a precise, localized code edit that the pull request author can apply directly from the review. To make one, select the relevant lines in the pull request’s Files changed tab, insert and edit a suggestion block, then add it to your review. Suggestions make a proposed edit easy to apply; they do not certify that it is correct or approve the pull request.
What a GitHub suggested change does
A suggested change is an exact code edit embedded in a pull request review comment. Instead of describing a small replacement for the author to type, a reviewer can put the replacement in a suggestion block. An eligible user can then apply it from the pull request interface.
GitHub’s quickstart for reviewing pull requests recommends suggesting an edit when you know the exact change you want the author to apply. The feature is best suited to changes that fit the selected lines; it is not a general-purpose way to implement a large or uncertain redesign.
How to create a suggestion in a pull request
- Open the pull request and select Files changed.
- Start a comment on the line or lines you want changed.
- In the comment toolbar, insert a suggestion block.
- Edit the code inside the block to show the proposed replacement or addition. Include a comment explaining why the change helps, especially if the edit’s purpose may not be obvious.
- Add it to the review by selecting Start a review or Add review comment.
These steps follow GitHub’s documented review quickstart. The author still needs to judge whether the proposed code fits the change’s requirements and intent.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors#1 Best Overall
Apply one suggestion or combine several
Someone with write access to the repository can apply a suggestion. GitHub also supports staging multiple suggestions and applying them as a batch. Either applying one suggestion or applying a batch creates one commit on the pull request’s compare branch. In a batch, the selected edits travel together in that commit.
| Choice | Best fit | Commit result |
|---|---|---|
| Apply one suggestion | One localized edit that is ready to accept | One commit for the applied suggestion |
| Apply a batch | Several compatible suggestions that should be accepted together | One commit containing the selected suggestions |
| Make a broader code update | Feedback that needs a wider implementation or changes beyond the suggested lines | Address it with code changes and push a new commit or commits to the pull request branch |
For an applied suggestion or batch, each person whose suggestion is included is recorded as a co-author. The person who applies the changes is also a co-author and is the committer. GitHub documents these application and attribution details in Incorporating feedback in your pull request.
Check permissions, especially for a fork
Applying a suggestion requires write access. If the pull request comes from a fork, an upstream maintainer can apply it only when the author has allowed edits from maintainers and the person applying it has write access to the upstream repository. If the apply option is unavailable, check these access conditions before assuming the suggestion itself is at fault. GitHub explains the requirements in its feedback incorporation guidance.
Choose a suggestion, a comment, or a wider update
Use a suggestion for a clear, local edit
A suggestion is a good fit when you know the exact replacement or addition and it can be expressed in the selected lines—for example, a small correction or a directly implementable refinement. A short explanation alongside the proposed code helps the author understand its purpose.
Use a regular comment when the solution is open
If you are asking a question, pointing out a problem without knowing its fix, or proposing an approach that needs discussion, write a regular review comment. A code block can look authoritative, but the suggestion mechanism does not prove that the edit is correct, complete, or compatible with the author’s intent.
Use a broader update when the change exceeds the selected lines
Feedback about an architectural choice or code beyond the selected lines may require a different implementation. The author should first understand the comment’s intent, then make an appropriate wider update and push it to the pull request branch. GitHub’s review-resolution guidance distinguishes direct suggested edits from feedback often handled with changes and new commits.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A suggestion is not a review decision
A suggested edit is a comment and a possible code change, not an approval or merge decision. GitHub’s review actions have separate meanings: Comment provides feedback, Approve signals that the changes are ready to merge, and Request changes flags feedback to address. Submit the review with the decision that reflects your assessment, separately from whether you included a suggestion. Whether a request-changes review blocks merging depends on the repository’s configured rules and settings; see GitHub’s guidance on reviewing proposed changes.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Free tools Windows power users keep installed
One-click scans. No signup required.
