Interactive rebase drag-and-drop does not persist changes when GitKraken runs offline

Question

Goal: Verify whether GitKraken’s interactive rebase drag‑and‑drop interface remains fully functional when the client is started without network connectivity, i.e., whether commit reordering, squashing, rewording, editing or dropping operations succeed and are reflected in the local repository after the session ends.

Constraints/uncertainty: GitKraken’s licensing model may require periodic online validation for paid features; it is not documented whether the interactive rebase tool is considered a core feature or a premium one that could be disabled offline, leaving the behavior uncertain.

Specific questions: Does GitKraken allow all interactive rebase actions without an active internet connection? Are any of those actions limited or degraded in offline mode? Does the client restore full interactive rebase capability after reconnecting and completing any required license check?

Tasadduq Burney · Answer

AnswerInteractive rebase drag-and-drop in GitKraken modifies the local repository via the local Git binary. Commit reordering, squashing, rewording, editing and dropping are written to the local .git directory and reflog, so the changes persist after the session ends even when GitKraken is started without network connectivity. The underlying Git operation does not require internet.GUI availability can be affected by license validation. GitKraken uses a periodic heartbeat to validate Pro or Enterprise subscriptions. If the client has a valid cached session from a recent online check, the interactive rebase UI remains usable offline. If validation has expired or fails while offline, the application may prompt for login or revert to a restricted Free mode. In that case the interface for a premium-classified feature may become inaccessible, but any rebase already completed is not reverted because it is already committed locally.Confirmed factsGitKraken is a GUI wrapper for the local Git binaries. Interactive rebase actions execute locally on the filesystem.Local repository changes made through the GUI are stored in .git and persist regardless of connectivity status.Reconnecting and completing a license check restores full GUI feature access immediately.Likely explanationLicense validation governs UI feature access, not Git data persistence. Offline mode may prevent sync of global user profiles or cloud settings, and premium GUI tools may be gated after the offline grace period expires. The exact grace period and whether interactive rebase is treated as core or premium varies by version and license tier.Verification steps for this caseDisable network interfaces and open the repository in GitKraken.Open the interactive rebase view and perform a drag-and-drop reorder, squash or drop on a local branch.In a terminal at the project root run:git log --oneline -n 10Confirm commit hashes and order match the UI.Restart GitKraken while still offline and verify the graph reflects the updated local state.One diagnostic detail that changes the recommendation: which license tier you are using, Free, Pro or Enterprise, and whether the client was online with a valid session within the last grace window. That determines whether the interactive rebase UI will be accessible offline or only after reconnection.

Interactive rebase drag-and-drop does not persist changes when GitKraken runs offline

1 answer

Answer

Confirmed facts

Likely explanation

Verification steps for this case

Your perspective belongs here.

0 question comments