Please see contribution-guide.org for general details on what we expect from contributors. Thanks!
There are a number of systems in place to help ensure gevent is of the highest possible quality:
- Builds on Travis CI automatically submit updates to coveralls.io to monitor test coverage. Pull requests that don't feature adequate test coverage will be automatically failed.
- Likewise, builds on Travis CI will automatically submit updates to landscape.io to monitor code health (adherence to PEP8, absence of common code smells, etc). Pull requests that decrease code health will be automatically failed.
- A test suite is run for every push and pull request submitted. Travis CI is used to test on Linux, and AppVeyor runs the builds on Windows. Pull requests with tests that don't pass will be automatically failed.
Pull requests that don't pass those checks will be automatically failed. But don't worry, it's all about context. Most of the time failing checks are easy to fix, and occasionally a PR will be accepted even with failing checks to be fixed by the maintainers.