34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# Support
|
|
|
|
Xbin uses public GitHub issues as its primary support channel so questions, fixes, and decisions stay searchable for future contributors.
|
|
|
|
## Choose the right path
|
|
|
|
- **Bug report**: use the bug report issue template when something is broken or regressed.
|
|
- **Feature request**: use the feature request template when proposing a scoped improvement.
|
|
- **Question**: use the question template for setup, deployment, or usage help.
|
|
- **Security issue**: follow [SECURITY.md](./SECURITY.md) and report it privately.
|
|
- **Code of conduct concern**: follow [CODE_OF_CONDUCT.md](./CODE_OF_CONDUCT.md) and report it privately.
|
|
|
|
## Before opening an issue
|
|
|
|
- Read the [README](./README.md) and [CONTRIBUTING.md](./CONTRIBUTING.md).
|
|
- Search existing issues and pull requests first.
|
|
- Try to reproduce the problem on the latest code when possible.
|
|
- Remove secrets, tokens, account IDs, and sensitive logs from anything you share publicly.
|
|
|
|
## What to include
|
|
|
|
Good support requests usually include:
|
|
|
|
- what you are trying to do
|
|
- what you expected
|
|
- what happened instead
|
|
- reproduction steps
|
|
- relevant environment details
|
|
- sanitized logs, screenshots, or request samples
|
|
|
|
## Response expectations
|
|
|
|
Support is handled on a best-effort basis. If you have not received a response after 7 days, a polite follow-up on the same issue is welcome.
|