Help shape Revus
Good reports create good software.
Use the public issue tracker for most conversations. Keep sensitive security details private and include enough context for someone else to reproduce the problem.
Report a bug
Share a reproducible problem with the environment and steps that led there.
02 / IdeasRequest a feature
Describe the workflow you want to make clearer, faster, or more predictable.
03 / SupportAsk for help
If an issue is not a bug report or feature request, start a conversation by email.
Before you send
Give the next person a useful starting point.
A short, specific report is easier to act on than a long description without a path to reproduce it.
Frequently asked
Answers without the fine print maze.
Is Revus ready to download?
The desktop app is in an early foundation milestone. Download cards show the state of each build target and never point to placeholder files.
Where should I report a bug?
Use the public issue repository for reproducible bugs, feature requests, and general support questions. Include your OS, Revus version, Git version, and the shortest reproduction you can share.
Does Revus send my repositories anywhere?
Core repository workflows are designed to run against repositories on your machine. Optional online integrations, when available, may communicate with their respective providers.
Will Revus always be free?
Revus is free during the initial release phase. The project keeps future optional professional or hosted capabilities configurable; any change in terms will be communicated clearly before it happens.