GitKraken commit history page size across local and remote branches

Question

The goal is to confirm whether GitKraken's configured commits-per-page limit applies consistently across local commits and remote-tracking branches in the commit graph view.
The pagination control appears as numbered buttons, with an optional infinite-scroll or Load-more alternative. Documentation indicates the setting may not apply uniformly across repository types or branch states, but it does not specify whether switching from a local branch to a remote-tracking branch resets or preserves the page size and current offset. This should be confirmed against the installed client because the documentation does not state whether the limit is branch-scoped.
This matters for large repositories where rapid page loading can affect responsiveness. The question assumes the standard GitKraken desktop commit graph and does not cover submodules or custom merge views.
Does the commits-per-page preference remain active when moving between local and remote branches? Is the page offset retained across branch switches? Should teams disable infinite scroll for very large histories to avoid repeated full-history loads?

Tasadduq Burney · Answer

Pagination Behavior in GitKraken
The commits-per-page preference in GitKraken is a global application setting. It applies consistently across both local commits and remote-tracking branches within the commit graph view; it is not scoped to individual branches.

Offset and State Persistence
While the page size limit remains active, the page offset is not retained when switching branches. Switching from a local branch to a remote-tracking branch (or vice versa) triggers a re-render of the graph to align with the new HEAD. This action resets the view to the top of the history for the selected branch.

Performance Considerations for Large Histories
In repositories with exceptionally large histories, the choice between pagination and infinite scroll impacts system responsiveness differently:

Infinite Scroll: As you scroll, GitKraken instantiates more commit nodes in the UI layer. In very large repositories, this can increase memory consumption and lead to UI lag.
  Pagination: Limits the number of nodes rendered at once, which can stabilize performance on lower-spec hardware or massive commit logs.

For teams managing repositories with tens of thousands of commits, disabling infinite scroll in favor of strict pagination is recommended to prevent repeated full-history loads and reduce memory overhead.

Verification Steps
To verify these behaviors in your current version of GitKraken:

Navigate to Preferences > General to confirm your global commit history limits.
  Scroll deep into a local branch's history to load several pages of commits.
  Switch to a remote-tracking branch (e.g., origin/main) and observe that the view resets to the top.
  Switch back to the original local branch to confirm the offset has reset and does not return to the previous scroll position.

Diagnostic Detail: Please specify if you are using the GitKraken Desktop client or the Cloud/Web version, as rendering engines for the graph may differ in how they handle DOM virtualization.

GitKraken commit history page size across local and remote branches

1 answer

Pagination Behavior in GitKraken

Offset and State Persistence

Performance Considerations for Large Histories

Verification Steps

Your perspective belongs here.

0 question comments