Skip to content

Reflog

You can use the Reflog activity to view HEAD or branch history, showing every operation that moved a ref. The Reflog records resets, rebases, force-pushes, and branch deletions, so you can recover a commit even after the branch that pointed to it is gone.

To show the Reflog activity, click its activity-bar icon or click Git > Reflog.

Reflog entries are listed newest first. In standard mode, each entry shows:

  1. The operation badge and the commit hash. Click the hash to open the commit.
  2. The message summary, when available.
  3. The time since the operation occurred, and the number of files changed when there are any.

Click the Toggle compact mode icon to show each entry on one line.

To open a reflog in a separate tab, right-click the reflog and click Open in New Tab.

Filter reflogs

Click the Show filters icon to open the filter panel. Enter a message, operation, or short commit hash in Search reflog. Use Ref to choose HEAD or a local branch. Use Operation to choose a Git operation. Press Ctrl+F (Cmd+F on macOS) to open the panel and focus the search field.

The line above the list shows the number of entries and each filter that is set, for example Showing 12 of 80 entries on main with operation checkout. Click a filter name to open the panel and focus its control. Click Clear filters to clear all of the filters and show HEAD again.

Reflog Entry view

Click a reflog entry to open the reflog in the Reflog Entry view. The Reflog Entry view displays the following information.

  • Reflog ID: The most recent reflog entry is assigned the HEAD@{0} ID.
  • Git operation badge: The type of operation the reflog recorded.
  • Timestamp: The amount of time since the operation occurred.
  • Operation message: The message of the operation.
  • Commits: The commits made before and after the reflog entry.
  • Files changed: The number of files in the reflog entry.

Reflog actions

In the Reflog Entry view, click the following action icons to perform a reflog action.

IconAction
Show in CommitsShows the matching commit in the Commits activity.
Create branch from here…Creates a branch at the reflog entry, with an option to switch to it. See Create a branch from a commit, tag, or reflog entry.
Cherry-pick this commitCherry-picks the reflog onto the current branch.
Copy hashCopies the commit hash of the reflog.
Reset —soft (moves HEAD only)Moves HEAD to the entry’s commit without changing staged content or working files.
Reset —mixed (moves HEAD + unstages)Moves HEAD to the entry’s commit and clears staging without changing working files.
Reset —hard (discards changes)Moves HEAD to the entry’s commit and discards uncommitted changes to tracked files.

You can also right-click an entry in the Reflog activity. The menu has Show in Commits, Create branch from here…, Cherry-pick this commit, Checkout (detached HEAD), and a Reset here action for each reset mode.

Each reset asks you to confirm. If the repository changes before the reset starts, Zide does not reset. See The repository changed before an action could start.

If a cherry-pick cannot start, Zide lists the reasons. It offers Open Staging or Stash Changes and Review when those actions can help. See A merge, revert, or cherry-pick did not start.