0.4.0

Added

• In file history, an expanded commit shows that file's diff, and Newer/Older buttons or the arrow keys step through the file's commits.
• The arrow keys move the focus between commit rows.

Fixed

• A merge commit's file list shows only what changed against its first parent, not against every parent.

What's Changed

• Git Graph 0.4.0: file diff and commit stepping in file history by @Luis85 in #6

Full Changelog: 0.3.0...0.4.0

0.3.0

Added

• A "Show history of the active file" toggle in the pane header lists only the commits that touched the file open in the editor (renames followed), as a flat list; switching files re-filters, and turning it off restores the graph.

What's Changed

• Git Graph: file history toggle for the active file by @Luis85 in #4
• Git Graph 0.3.0: file history toggle by @Luis85 in #5

Full Changelog: 0.2.1...0.3.0

0.2.1

Changed

• For a vault that is a folder inside a larger repository, the changes row now counts and lists only files under the vault, so it no longer goes stale on edits the pane cannot see.

Fixed

• The release workflow now also waits for CI's npm audit job before publishing, instead of publishing as soon as the build and test runs are green.
• With "Refs to show" on Auto, a stale origin/HEAD (the remote's default branch renamed or pruned) no longer makes the whole graph fail with "bad revision".
• A file whose name begins with two dots (such as ..notes.md) now opens from the commit and changes lists instead of being reported as outside the vault.
• A repository with uncommitted files but no commits yet shows the changes row instead of only "No commits yet".
• When a page of commits ends on a merge whose parents are all on the next page, each parent now gets its own line off the bottom of the graph instead of all of them overlapping in one.

What's Changed

• Polish: answer the #1/#2 review threads and the marketplace scan by @Luis85 in #3

Full Changelog: 0.2.0...0.2.1

0.2.0

Changed

• The graph lays out lanes the way VS Code's Git Graph does: the top commit's first-parent chain keeps the left lane all the way down, a side branch runs beside the graph until its parent's row and curves in there, and lanes slide left as soon as a line to their left ends, instead of a lane dying into a side branch and leaving a permanent gap.

What's Changed

• Git Graph 0.2.0: VS Code-style lane layout by @Luis85 in #2

Full Changelog: 0.1.0...0.2.0

0.1.0

Added

• Git Graph, a read-only side pane drawing the vault's git repository as VS Code's
  Source Control graph does: colored lanes, commit subjects, authors, dates, branch, tag
  and remote badges, and the current HEAD. Open it from the ribbon or Git Graph: Open.
• Clicking a commit expands its full message and the files it touched; clicking one of
  those files opens it in the editor, with a notice when it is outside the vault or gone.
• A changes row above the newest commit carries the uncommitted change count; expanding it
  lists the working-tree files with their status, and clicking one opens it.
• The pane refreshes itself when the repository's git state changes, and picks up
  working-tree edits within about half a second while it is open. Git Graph: Refresh
  re-reads on demand.
• Settings for the git executable, which refs to show, commits per page, whether to show
  the working-tree changes row, and relative or absolute dates.
• Deleted files in a file list are shown struck through and cannot be opened; relative
  dates count months and years on the calendar rather than in 30-day blocks.

What's Changed

• Git Graph 0.1.0: the plugin, its harness and release tooling, and the review-fixes pass by @Luis85 in #1

New Contributors

• @Luis85 made their first contribution in #1

Full Changelog: https://github.com/Luis85/obsidian-git-graph/commits/0.1.0