This project is owned by the Verification as a Service team. To contribute to this project, you'll need to follow the fork-and-PR workflow.
- We follow PEP 8 for coding standards.
- Any PRs must pass all automated checks to be approved.
This library powers production services. New features must be approved by the maintainer. PRs for bug fixes are welcome, but new features or breaking changes should be associated with a discussion. Please use the Github issue tracker to kick off the discussion. Rough ideas to fully fleshed out designs are welcome!
PRs can be submitted at any time, however if it's not ready to be merged, please add the "work in progress" label.
- You must create your own fork, and a feature branch on that fork.
- Try not to introduce system wide breakages.
- Your feature must not cause any failure of current tests.
- You need to show testing compliance for your added code.
- Please write copious PR comments, so you remember what you did.
- If appropriate, update the README.md with any relevant details of changes you made which affect the project. This may include changes to the interface, new environment variables, new ports, useful new file locations, added or removed dependencies, and anything else that will affect other contributors.
- We will contact you when you create your PR. In some cases, we may just approve it for merge.