This repository is the public issue tracker and community feedback space for Revus, a modern desktop Git client.
The Revus application source code is maintained separately in a private repository. This repository contains no application source code. It is intended for bugs, feature requests, improvements, support questions, and other product feedback.
Please use this tracker to:
- Report a reproducible problem with Revus
- Request a new feature
- Suggest an improvement to an existing workflow, interface, document, accessibility experience, or performance characteristic
- Ask a usage question or request support
- Share general product feedback
- Review known issues and planned improvements as they are recorded
Before opening an issue, search existing issues and choose the most relevant form:
Include the requested environment details, a concise description, and enough context for another person to understand the situation. For bugs, provide clear reproduction steps and distinguish expected behavior from what actually happened. Add screenshots or logs when they clarify the report, but remove credentials, tokens, private repository URLs, email addresses, usernames, and proprietary code first.
Feature requests and improvements are most useful when they explain the problem or workflow, the desired outcome, and the benefit to users. A well-described request is not a promise of implementation; proposals are evaluated alongside project priorities, technical constraints, maintenance cost, and community value.
Do not report security vulnerabilities through public GitHub Issues. Follow the private reporting instructions in SECURITY.md.
Start with SUPPORT.md for guidance on where to ask questions and what information to include. Please keep discussions respectful, specific, and constructive. The Code of Conduct applies to this repository and its community spaces.
This repository is the public issue-tracker setup for Revus. Its forms and guidance are designed to collect actionable feedback while the application source remains in a separate private repository. This tracker does not make claims about release dates, pricing, platform availability, or particular application capabilities.
The recommended label structure is documented in docs/issue-guidelines.md. Labels help separate issue type, triage state, priority of follow-up, and common areas such as accessibility or performance.
The documentation and configuration in this repository are available under the MIT License.