# Support Different question types route to different places. Please use the channel that matches your request — it gets you to the right person faster and keeps the issue tracker focused. ## Bug reports Found a defect? Open a [GitHub issue](https://github.com/openlinker-project/openlinker/issues/new) with the `bug` label. Include: - Reproduction steps (the smaller the better). - Expected vs. actual behaviour. - Affected version (commit SHA or `main`). - Relevant logs, with any secrets redacted. ## Security reports **Do not open a public issue or pull request for security vulnerabilities.** Follow the responsible-disclosure process in [SECURITY.md](./SECURITY.md). Reports go through GitHub Security Advisories, which keeps the thread private to maintainers until a fix is published. ## Feature requests OpenLinker will use [GitHub Discussions](https://github.com/openlinker-project/openlinker/discussions) for design conversations once Discussions is enabled in repo settings (tracked alongside the org transfer in [#641](https://github.com/openlinker-project/openlinker/issues/641)). In the interim, open an [issue](https://github.com/openlinker-project/openlinker/issues/new) with the `enhancement` label and describe: - The operator workflow or integration scenario the feature unlocks. - The proposed shape (API surface, UI affordance, or capability port). - Which platforms or bounded contexts it touches. ## General questions Usage questions, "how do I …", and design discussions belong on [GitHub Discussions](https://github.com/openlinker-project/openlinker/discussions) once it is enabled. In the interim, open an issue with the `question` label. Please search closed issues and the [documentation](./docs/) first — many setup questions are already covered by `docs/dev-environment.md` and `CONTRIBUTING.md`. ## Commercial / enterprise support A commercial-support offering is planned but not available today. Tracked alongside the OpenLinker domain in [#642](https://github.com/openlinker-project/openlinker/issues/642); this section will be updated when a maintained channel exists. ## Code of conduct All community spaces — issues, pull requests, and (once enabled) Discussions — are governed by our [Code of Conduct](./CODE_OF_CONDUCT.md).