Thank you for your interest in contributing to SubmitQueue! Whether you are reporting a bug, suggesting a feature, improving documentation, or writing code, your contribution is welcome.
- Read the Development Setup guide for prerequisites, building, and running tests.
- Review the Architecture Guide to understand project layout, conventions, and code style.
- Check the Testing Guide for testing patterns and requirements.
- Fork the repository and clone your fork.
- Create a feature branch from
main:Use branch naming likegit checkout -b yourname/short-description
yourname/short-descriptionorfix/issue-123. - Make your changes, following the project conventions.
- Add or update tests as appropriate.
- Run
make gazelleif you added or removed Go files. - Run
make testto ensure unit tests pass. - Commit with a clear, descriptive message.
- Push to your fork:
git push origin yourname/short-description
- Open a pull request against
main.
- Keep PRs focused on a single change.
- Reference related issues: use
Closes #123for fixes orPart of #123for incremental work. - Include tests for new functionality.
- Ensure all existing tests pass (
make test). - Ensure CI passes before requesting review.
- Follow the existing code style and patterns described in the Architecture Guide.
- Fill out the PR template with a description, motivation, and test plan.
All submissions require review before merging. We use GitHub pull requests for this purpose. A maintainer will review your PR and may request changes.
Use GitHub Issues to report bugs or request features. Please use the provided issue templates and check existing issues before creating a new one.
- Bug reports and feature requests — GitHub Issues
- Questions and discussions — open an issue with the
questionlabel
This project adheres to the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code.
By contributing to SubmitQueue, you agree that your contributions will be licensed under the Apache License 2.0.