Skip to main content
GitLens brings advanced Git insights into the Code IDE so you can see how files evolved, who changed a line, and search or compare commits without leaving your dbt™ workflow. You open it from a dedicated icon in the left sidebar.
Prerequisites
  • A Paradime workspace with a connected git repository.
  • The Code IDE open on that repository.
GitLens works the same in both Git Lite and Git Advanced modes.

​
Steps

1

Open File History for a file

File History shows a chronological list of every commit that affected a file, so you can understand how it evolved and spot major changes made by your team.
  1. Select a file in the Code IDE.
  2. Click the GitLens icon in the left sidebar.
  3. Open the File History tab in the GitLens panel to see the list of commits.
  4. Click a commit to view the detailed changes it introduced.
2

Inspect Line History and blame annotations

Line History shows who changed specific lines and when, through inline annotations next to each line. This helps you understand the context behind a change or find the author for collaboration or debugging.
  1. Open any file in the Code IDE.
  2. Click a line of code to see inline annotations with the most recent author and commit date.
  3. Hover over an annotation to see more detail about that commit.
  4. For the full history of a line (beyond the most recent commit), click the GitLens icon in the left sidebar, then reselect the line to view its complete change history.
3

Search and compare commits

Search & Compare lets you find commits, changes, or contributions across the whole project, and compare branches or references.
  1. Click the GitLens icon in the left sidebar.
  2. Open the Search & Compare tab in the GitLens panel.
  3. Choose one of the two options:
Option 1: Search commits
  • Select your search type (Author, Message, or File).
  • Enter search terms (for example, an author name like fabio or a message keyword like fix).
  • Review the results and click a commit to view its details.
Option 2: Compare references
  • Select the first reference (branch, tag, or ref) to compare.
  • Select the second reference to compare against.
  • Review the comparison to see the differences between the two references.
You know GitLens is working when the GitLens panel lists commits for a selected file and inline blame annotations appear next to lines of code. If annotations do not show, confirm the file is tracked in your connected git repository.

​
Next steps

Resolve merge conflicts

Handle conflicting changes when you merge branches.

Sign your commits

Add SSH-based commit signing for verified commits.

GitLens reference

Full GitLens feature reference in the Code IDE.

Version control in the Code IDE

How version control works across the Code IDE.

Related topics

Configure signed commits with SSH keysGitLensVersion ControlUse Git AdvancedGit Advanced