|
| 1 | +# Contributing to JaxADi |
| 2 | + |
| 3 | +We're thrilled that you're interested in contributing to JaxADi! This document outlines the process for contributing to this project. |
| 4 | + |
| 5 | +## How to Contribute |
| 6 | + |
| 7 | +There are many ways to contribute to JaxADi: |
| 8 | + |
| 9 | +1. Reporting bugs |
| 10 | +2. Suggesting enhancements |
| 11 | +3. Writing documentation |
| 12 | +4. Submitting code changes |
| 13 | + |
| 14 | +### Reporting Bugs |
| 15 | + |
| 16 | +1. Check the [issue tracker](https://github.com/based-robotics/jaxadi/issues) to see if the bug has already been reported. |
| 17 | +2. If not, create a new issue. Provide a clear title and description, as much relevant information as possible, and a code sample or executable test case demonstrating the bug. |
| 18 | + |
| 19 | +### Suggesting Enhancements |
| 20 | + |
| 21 | +1. Check the [issue tracker](https://github.com/based-robotics/jaxadi/issues) to see if the enhancement has already been suggested. |
| 22 | +2. If not, create a new issue. Clearly describe the enhancement, why it would be useful, and any potential drawbacks. |
| 23 | + |
| 24 | +### Writing Documentation |
| 25 | + |
| 26 | +Good documentation is crucial. If you notice any part of our documentation that could be improved or expanded, please let us know or submit a pull request with your suggested changes. |
| 27 | + |
| 28 | +### Submitting Code Changes |
| 29 | + |
| 30 | +1. Fork the repository. |
| 31 | +2. Create a new branch for your changes. |
| 32 | +3. Make your changes in your branch. |
| 33 | +4. Add or update tests as necessary. |
| 34 | +5. Ensure the test suite passes. |
| 35 | +6. Update the documentation as needed. |
| 36 | +7. Push your branch and submit a pull request. |
| 37 | + |
| 38 | +## Pull Request Process |
| 39 | + |
| 40 | +1. Ensure your code follows the project's style guidelines. |
| 41 | +2. Update the README.md or relevant documentation with details of changes, if applicable. |
| 42 | +3. Add tests for your changes and ensure all tests pass. |
| 43 | +4. Your pull request will be reviewed by the maintainers. They may suggest changes or improvements. |
| 44 | +5. Once approved, your pull request will be merged. |
| 45 | + |
| 46 | +<!-- TODO: |
| 47 | +
|
| 48 | +## Style Guidelines |
| 49 | +
|
| 50 | +We use Ruff to enforce our code style and linting rules.... |
| 51 | +```bash |
| 52 | +pip3 install pre-commit |
| 53 | +``` |
| 54 | +```bash |
| 55 | +pre-commit install |
| 56 | +``` --> |
| 57 | + |
0 commit comments