Use GitHub Discussions for:
- setup questions
- workflow ideas
- comparison questions
- show-and-tell posts
Use the repository issue tracker for:
- bug reports
- reproducible build or verification failures
- documentation corrections
- confirmed problems with supported commands or workflows
Before opening an issue, check:
README.mddocs/index.mddocs/proof-and-faq.mddocs/governance-runbook.mddocs/testing.mddocs/release-readiness.md
For sensitive vulnerabilities, do not treat the issue tracker as the default
intake path. This repository is public and GitHub private vulnerability
reporting is enabled. Use the private reporting route described in
SECURITY.md.
Good support requests usually include:
- the command that failed
- the branch or commit
- the affected file path or workflow
- expected vs actual behavior
- relevant logs with secrets removed
This project is maintained on a best-effort basis.
Support is not guaranteed for:
- private forks with large local divergence
- unpublished internal environments
- requests that require access to private credentials or infrastructure
- external security reports that skip the owner-contact path in
SECURITY.md
If the problem is clearly in the upstream ShadcnBrief project rather than this repository's integration layer, maintainers may redirect you to the upstream project.