Orient first.
Changes, history, branches, tags, and remotes share one readable workspace.
Revus 1.3.10
Revus is designed around the moment before a Git command: understand the repository, choose the right target, and make the move without losing the thread.
The design rule
Put the action next to the thing it changes.
Changes, history, branches, tags, and remotes share one readable workspace.
The next action lives beside the branch or commit it changes—not in a detached command center.
When Git needs attention, Revus brings the operation forward with an honest path to resolution.
Capability map
No mystery roadmap badges here. This is the current product surface, written for real repository work.
Start with context
Open a repository and move between its changes, history, branches, and remotes without losing context.
Know the state
Review changed, staged, untracked, binary, and image files before deciding what to include in a commit.
See the story
Follow branches and merges in a graph, then inspect commit details, blame, file history, or the reflog in context.
Make the next move
Merge, rebase, cherry-pick, revert, or create a tag from the branch or commit you are already reviewing.
Stay in control
When Git pauses for a conflict, see the active operation and its available continue, skip, abort, and resolution actions.
Keep ceremony low
Set up a remote or initialize a repository, then fetch, pull, push, and publish when the work calls for it.
Stay connected
Open the matching commit, repository, review, or pull request on its provider while keeping your local work in Revus.
Go deeper
Use interactive rebase, patch workflows, external tools, and diagnostics when you need them; keep them out of the way otherwise.
Stay in the flow
Create tags, rename branches, edit remotes, confirm recovery actions, and enter messages in focused Revus dialogs.
Built for trust
Revus uses the native Git CLI and keeps core repository work on your machine. Online integrations are visible, optional, and provider-specific.