[pitetb]

Summary

Adds an optional display mode that shows the working copy (local changes) as a node of the commit graph, "not yet attached" to the history, directly in the Dashboard view.
This allow us to see and commit current changes directly on the graph without needing to click on the "Loca changes" button on the left column. This feature exists in Gitkraken or Fork and is very convenient.

The option is disabled by default and can be toggled from the graph's advanced options menu (⚙ → Local changes as graph node). The existing Local Changes page is unchanged.

Behavior

When the option is enabled and the working copy has changes, a pseudo commit "Local changes (N)" is inserted at the top of the history:

• Graph: drawn as a dashed hollow dot, linked to HEAD with a dashed line. Only that link is dashed; the rest of the branch is drawn as usual.
• Select the node: the details panel shows the full local changes view (stage/unstage, diff, commit message box).
• Select the node + one commit: compares that commit with the worktree (same as Compare with Worktree).
• Context menu: Stash, Discard all changes, Open in Local Changes page.
• Double-click: opens the Local Changes page (no checkout).
• After commit / stash / discard: if the node was selected and disappears, the current HEAD is selected (then the new HEAD once commits are refreshed).
• The node is not shown for bare repositories, or when HEAD is not part of the loaded history (branch filters, commit limit).
• Author / SHA / time columns are left empty for this row, and Ctrl+C ignores it.

Implementation

• Models.LocalChangesNode: new Commit subclass with a sentinel SHA and an observable Count; Commit.IsLocalChanges (virtual) is used by views and graph.
• ViewModels.Histories: inserts/removes/updates the node (ApplyLocalChangesNode / RefreshLocalChangesNode) without regenerating the graph when only the count changes; selection handling for the new cases.
• ViewModels.Repository: refreshes the node after querying local changes.
• Models.CommitGraph: new DotType.LocalChanges and Path.IsDashed; the node's path is split at HEAD (PathHelper.Detach()) so that only the link to HEAD is dashed.
• Views.CommitGraph: renders dashed paths and the new dot type.
• Views.Histories: row template, WorkingCopy data template in the details panel, menu entry, context menu, double-click handling.
• Preferences.ShowLocalChangesInGraph: new global preference.
• Localization: new keys added to all locales. The node label uses a DynamicResource, so it follows runtime locale changes. Non-English/French translations were not reviewed by native speakers; corrections welcome.

Known limitations

• In the two-columns history layout, the details panel may be narrower than the local changes view's minimum width.
• The details panel's top-right buttons (open as standalone / collapse) overlap the top-right corner of the embedded local changes view.

Tested

• Toggle the option on/off from the graph menu; check that other open repository tabs update when shown again
• Node rendering with HEAD at the top, HEAD not at the top (newer branch above), detached HEAD
• Select node → stage/unstage, diff, commit from the details panel
• Select node + commit → compare with worktree
• Commit / stash / discard while the node is selected → HEAD gets selected
• Merge/rebase in progress, branch filters, first-parent only, bare repository
• Vertical and two-columns layouts
• Switch UI language at runtime → node label is updated

[tib8]

Oh I did almost the same #2816

[pitetb]

One or another, I'm fine as it's merged!...