GitKraken GUI and Git CLI: Commit Graph Synchronization Latency

Interoperability between GitKraken and Local Git CLI

GitKraken operates as a visual wrapper around the local Git installation, maintaining a real-time representation of the commit graph. When changes are made to the repository state via the command line interface (CLI), the GUI must detect these modifications to refresh the visual tree and update the HEAD pointer.

There is an uncertainty regarding the exact mechanism and timing of the refresh cycle when external CLI commands modify the index or commit history. In high-frequency commit environments or large repositories, the latency between a git commit command and the GUI update can vary.

• Does GitKraken rely on a polling interval or a filesystem watcher to detect external changes?
• What is the expected synchronization latency for the commit graph to reflect a CLI-driven HEAD movement?