|
| 1 | +# OpenAPI Pydantic Contribution Guide |
| 2 | + |
| 3 | +We welcome all contributions! |
| 4 | + |
| 5 | +## Issues |
| 6 | + |
| 7 | +Questions, feature requests and bug reports are all welcome as issues. When raising a bug or |
| 8 | +question, please include as much information as possible including the specific version you |
| 9 | +are using. |
| 10 | + |
| 11 | +## Pull Requests |
| 12 | + |
| 13 | +It should be very simple to get started and open a pull request, however for anything non-trivial |
| 14 | +please open an issue to discuss your intended change _before_ creating your PR. This avoids wasting |
| 15 | +time by ensuring that your changes will be accepted with fewer revisions down the line! |
| 16 | + |
| 17 | +### Local Development |
| 18 | + |
| 19 | +A [devcontainer](https://code.visualstudio.com/docs/devcontainers/containers) configuration is provided in the repo to get your environment setup automatically. Alternatively you can install [tox](https://tox.wiki/en/latest/) and [poetry](https://python-poetry.org/) manually. |
| 20 | + |
| 21 | +### Testing |
| 22 | + |
| 23 | +Please ensure all changes have good test coverage and are formatted correctly. You can run the test |
| 24 | +suite and linters using [tox](https://tox.wiki/en/latest/) - just run `tox` from the root of this |
| 25 | +repo to run the checks. These will also be run automatically in CI once your PR is opened. Don't |
| 26 | +worry about testing against every Ptyhon version - the CI action will do this for you! |
| 27 | + |
| 28 | +### Tagging |
| 29 | + |
| 30 | +When your PR is ready, please tag it with the appropriate tags: one of `feature`, `change`, `fix`, |
| 31 | +as well as `breaking` if you've introduced backwards-incompatible changes to the public API or |
| 32 | +behaviour. |
| 33 | + |
| 34 | +## Review |
| 35 | + |
| 36 | +We'll review your PR as soon as possible - either approving or requesting changes. Once the PR is |
| 37 | +approved, it will be merged into main and cut into the next release. |
| 38 | + |
| 39 | +## Releases |
| 40 | + |
| 41 | +The release schedule is not set in stone and will depend on the number of changes in flight, but where possible we'll look to cut a release with your changes as soon as possible. Once a new version is tagged, |
| 42 | +a package version is uploaded to PyPI automatically. |
0 commit comments