|
| 1 | +# Contributing |
| 2 | + |
| 3 | +Thanks for your interest in improving Tile38! |
| 4 | + |
| 5 | +## Issues |
| 6 | +- **Found a bug?** Please open an issue with a clear description and precise steps to reproduce. |
| 7 | + |
| 8 | +## Pull Requests |
| 9 | +- **Scope.** PRs are welcome for bug fixes and small, low-risk changes. |
| 10 | +- **Please coordinate first.** For large changes, such as new features, please file an issue and/or discuss it with a maintainer beforehand. |
| 11 | +- **Quality.** Keep PRs focused, include tests (where applicable), and update docs. |
| 12 | + |
| 13 | +## When Not to use a Pull Request |
| 14 | + |
| 15 | +Do NOT submit a Pull Request for: |
| 16 | + |
| 17 | +- Security-related changes. |
| 18 | +- Works in progress. |
| 19 | +- Changes that require design discussion, or are likely to be controversial. |
| 20 | +- Changes needing specialized or cross-subsystem review. |
| 21 | +- Large refactors or mechanical tree-wide changes. |
| 22 | +- Changes generated by AI tools. |
| 23 | + |
| 24 | +## AI Assisted Contributions |
| 25 | + |
| 26 | +We are not accepting AI assisted code into Tile38 at this time. |
| 27 | +This policy may change in the future. |
| 28 | +Please reach out if you have any questions or concerns regarding AI and Tile38. |
| 29 | + |
| 30 | +### Contributor Responsibilities |
| 31 | + |
| 32 | +- Monitor your Pull Request and respond to review feedback promptly. |
| 33 | +- Pull Requests may be closed if there is no response for **one month**. |
| 34 | + |
| 35 | +By submitting a contribution, you confirm you have the right to do so and grant Tile38 LLC the rights needed to use, modify, and redistribute your contribution as part of the project. |
| 36 | + |
| 37 | +If you have any questions or concerns regarding licensing, please contact us at licensing@tile38.com. |
| 38 | +For all other questions, contributing@tile38.com. |
0 commit comments