Developers
Contributing
Prepare a focused, tested change without private data.
Read the repository guide and Code of Conduct.
Pull request
- Explain the reproduced problem.
- Limit the change to one clear responsibility.
- Add or adapt tests.
- Document every command, variable, format or API change.
- List the validation commands you ran.
Test data
Never add a copyrighted book, private manuscript, API key, personal database or provider_credentials.json. Create small, fictional fixtures.
Git
Before committing:
git status --short
git diff --check
git diff --statInspect generated files, databases, outputs and logs before staging them.