Skip to content

Latest commit

 

History

History
60 lines (42 loc) · 1.46 KB

File metadata and controls

60 lines (42 loc) · 1.46 KB

Support

Where to Ask for Help

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.md
  • docs/index.md
  • docs/proof-and-faq.md
  • docs/governance-runbook.md
  • docs/testing.md
  • docs/release-readiness.md

Security Issues

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.

What Maintainers Need

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

Support Limits

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

Upstream Questions

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.