Robotest is an open source project.
Robotest is the work of many contributors. We appreciate your help! 🎉
Robotest contributors follow a code of conduct.
Robotest tends to have mostly Gravitational staff as contributors, so we're excited to get any outside contributions, including issues.
Security issues should be reported directly to security@gravitational.com.
If you are unsure if you've found a bug, please search Robotest's current issues.
If you're working on an existing issue, respond to the issue and express interest in working on it. This helps other contributors know that the issue is active, and hopefully prevents duplicated efforts.
If you want to work on a new idea:
- Submit an issue describing the proposed change and the implementation.
- Robotest maintainers will triage & respond to your issue.
- Write your code, test your changes. Run
make lint
,make test
andmake build
. Most importantly, communicate with the maintainers as you develop. - Submit a pull request from your fork.
If you wish to add new dependencies (anything that touches Dockerfile
s or go.mod
),
the new dependencies must be:
- licensed via Apache2 license
- approved by Gravitational staff
Robotest follows Semantic Versioning (semver) as described in the release documentation
Due to semver's strict requirements, patches that introduce new options or change behavior of the public API may need to wait for the next major or minor release for merge. Major & minor releases are issued on an as needed basis.
Robotest follows Go Code Review Comments,
in alignment with all of Gravitational's go code. Some (but not all) of the
guidelines are automated by Robotest's make lint
target. Please run
make lint
before submitting code to save reviewers the hassle of stylistic
nits.