Repository navigation
Contributing and Security
Search existing Issues and Discussions before opening a new item.
- Use Discussions for usage questions, environment help, ideas, and open-ended feedback.
- Use Issues for reproducible bugs, concrete feature requests, and documentation defects.
- Open or reference an issue before starting a large implementation to avoid duplicate work.
See Troubleshooting for the information required in a useful report.
- Fork
OtterMind/Chat2DB. - Open or reference the related issue.
- Create a branch for one focused change.
- Add or update tests proportional to the risk.
- Run local verification and record the commands and results.
- Include screenshots or recordings for UI changes.
- Open a focused, reviewable pull request.
The repository Contributing Guide and Code of Conduct are authoritative.
Do not report a security vulnerability through a public issue or discussion.
Use GitHub private vulnerability reporting. Include the affected edition and version, deployment type, impact, and reproduction steps. Remove passwords, API keys, tokens, private URLs, and production data from every attachment.
See the repository Security Policy for the Community trust boundary and reporting scope.
Chat2DB Community 5.3.0 and later uses the repository's current source-available license, based on Apache License 2.0 with additional conditions.
By contributing, you agree that the contribution is licensed under the project's current license and may be used by Chat2DB in commercial products or future releases under different license terms. Read the license before submitting a contribution.
Chat2DB Wiki
Community
Help
Project