GitLens Documentation

GitLens Code Suggest

Last updated: August 2025

What Is Code Suggest?

GitLens Code Suggest simplifies code review by allowing you to make suggestions and edits across the entire project, not just on changed lines.
Suggestions can be created within GitLens, GitKraken Desktop, or gitkraken.dev and attached to pull requests.

Reviewers can then view, accept, and apply these suggestions directly to the pull request branch.

GitLens Code Suggest view showing suggestion options
GitLens Code Suggest view

Start a Code Suggestion

  1. Open the GitLens Inspect Overview for your repository.
  2. Check out a branch with an open pull request.
  3. Select Start Review for PR #PR.
  4. Modify and save any files you want to include in the suggestion.
  5. When ready, select Suggest Changes for PR → provide a title → Create Code Suggestion.
Creating a Code Suggestion in GitLens
Creating a Code Suggestion

This action adds a comment on the pull request with two options:

  • Code Suggestion for #PR → review in gitkraken.dev
  • Locally on your machine → review in GitLens or GitKraken Desktop
Pull request comment with Code Suggestion options
Pull request with Code Suggestion comment

Review and Apply Suggestions Locally

  1. Select Locally on your machine.
  2. Open the suggestion in GitLens or GitKraken Desktop.
  3. Review changes file by file.
  4. Choose Apply to apply to your current branch, or select Apply to a Branch to apply to a new or existing branch.
Applying a Code Suggestion locally in GitLens
Applying a Code Suggestion locally

Review and Commit Suggestions in gitkraken.dev

  1. Select Code Suggestion for #PR to open the suggestion in gitkraken.dev.
  2. Review each file and its proposed changes.
  3. When ready, select Commit Suggestions.

This creates a new commit on the remote branch (shown under COMMIT SUGGESTIONS TO).

Accepting and committing Code Suggestions in gitkraken.dev
Committing suggestions in gitkraken.dev

Availability

Note: Code Suggest is currently supported only for repositories on GitHub.com.

Have feedback about this article? Did we miss something? Let us know!
On this page