We love your input! We want to make contributing to VisualEyes as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
We use GitHub to host code, to track issues and feature requests, as well as accept pull requests.
We Use Github Flow
Pull requests are the best way to propose changes to the codebase. We actively welcome your pull requests:
- Fork the repo and create your branch from
main. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
In short, when you submit code changes, your submissions are understood to be under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.
Report bugs using Github's issue tracker
We use GitHub issues to track public bugs. Report a bug by opening a new issue; it's that easy!
Great Bug Reports tend to have:
- A quick summary and/or background
- Steps to reproduce
- Be specific!
- Give sample code if you can.
- What you expected would happen
- What actually happens
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work)
- Clone the repository
- Create a new branch:
git checkout -b feature-name - Make your changes
- Run tests:
make test - Run linter:
make lint - Commit your changes:
git commit -m 'Add some feature' - Push to the branch:
git push origin feature-name - Submit a pull request
-
Install prerequisites:
- Go 1.21 or later
- PostgreSQL 14 or later
- Docker and Docker Compose (optional)
-
Set up the development environment:
# Install dependencies make deps # Build the project make build # Run tests make test
- Follow Go best practices and style guide
- Use meaningful variable and function names
- Write comments for complex logic
- Keep functions focused and small
- Add tests for new functionality
By contributing, you agree that your contributions will be licensed under its MIT License.