Contribution Guide
Vito is developed and maintained by its author, so pull requests are not accepted. You can still make a real difference by reporting bugs, sharing ideas, and giving detailed feedback. Clear, well-described issues are the most valuable contribution you can make.
Everything goes through GitHub Issues. Pick the template that matches your case:
| Template | Use it for |
|---|---|
| 🐞 Bug Report | Something is broken or behaves incorrectly |
| ✨ Feature Request | Something new that Vito doesn't do yet |
| 🔧 Improvement | Making an existing feature work better or easier to use |
| 📚 Documentation | Missing, outdated or unclear documentation |
| ❓ Question | Asking how to do something with Vito |
Before opening a new issue, search the existing issues and add your details to a matching one instead of creating a duplicate.
Reporting Bugs
Open a bug report. Please fill in every required field so the issue can be reproduced and fixed quickly:
- Installation type and Vito version — hover over the Vito icon in your dashboard to see the version.
- Area and server environment — which part of Vito is affected, and the OS, provider and services involved.
- What happened — a clear description of the bug.
- Steps to reproduce — the exact steps that trigger the issue.
- Expected behavior — what you expected to happen instead.
- Logs — relevant sections from
Vito Logs(bottom left corner of the dashboard) and failed jobs from theHorizon Dashboard. - Screenshots or recordings — whenever they help explain the problem.
Remove any secrets, tokens, passwords, or private keys from logs and screenshots before posting them.
Suggesting Features and Improvements
Open a feature request for something new, or an improvement for an existing feature. A good proposal explains:
- The problem you are trying to solve and why it matters to you.
- How you would expect the feature to work.
- Any workarounds or alternatives you have considered.
You can follow what is planned on the Roadmap.
Getting Help
Open a question or join the community on Discord.
Security Vulnerabilities
If you discover a security vulnerability within VitoDeploy, please do not open a public issue. Email Saeed Vaziry at sa.vaziry@gmail.com instead. All security vulnerabilities will be promptly addressed.
Sponsoring
If Vito is useful to you, you can support its development by sponsoring the project.
Code of Conduct
Violations of the code of conduct should be reported to Saeed Vaziry at sa.vaziry@gmail.com.
- Participants should embrace tolerance toward differing opinions.
- It is imperative for participants to use language and exhibit behaviors that avoid personal attacks and demeaning comments.
- When evaluating the statements and actions of others, it is crucial to presume positive intentions.
- Any behavior deemed as reasonably constituting harassment is strictly prohibited.