Orient first.
Changes, history, branches, tags, and remotes share one readable workspace.
Revus 1.2.0
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 land in the state that matters: changes, history, branches, and remotes stay one click away.
Know the state
See changed, staged, untracked, binary, and image files without losing the connection to the commit you are preparing.
See the story
Follow branches and merges in a readable graph, then open commit details, blame, file history, and reflog from the same surface.
Make the next move
Merge, rebase, cherry-pick, revert, and create tags from the branch or commit you are already looking at.
Stay in control
When Git stops on a conflict, Revus raises the operation at the top of the workspace with clear continue, skip, abort, and resolution paths.
Keep ceremony low
Configure remotes and initialize a repository once. Fetch, pull, push, and publish remain available without turning the workspace into a command center.
Stay connected
Open commits, repositories, reviews, and pull requests on the configured provider without giving up local control.
Go deeper
Interactive rebase, patch workflows, external tools, and diagnostics are available when needed and out of the way when they are not.
Stay in the flow
Create tags, rename branches, edit remotes, confirm recovery actions, and enter messages in focused Revus modals instead of browser prompts.
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.