Skip to content

SUPPORT.md

Latest commit

 

History

History
40 lines (30 loc) · 1.31 KB

SUPPORT.md

File metadata and controls

40 lines (30 loc) · 1.31 KB

Support

What To Use GitHub For

  • bug reports with clear reproduction steps
  • documentation fixes
  • narrowly scoped feature proposals
  • questions about repository behavior after you have checked the README and docs

What To Include

  • exact command(s) you ran
  • exact file path(s) involved
  • expected result
  • actual result
  • relevant logs or screenshots with secrets removed

What Is Out Of Scope

  • private support for custom forks or deployments
  • consulting or paid implementation work
  • guaranteed response times
  • hosted-service style support expectations
  • Linux/BSD or Windows desktop runtime support; the current public desktop support boundary is macOS-only and non-macOS desktop paths are unsupported

Security Reports

For vulnerabilities, do not open a public issue. Follow SECURITY.md and use the documented GitHub advisory form private path there first on the live public repository. An additional verified fallback private reporting channel is still not published in the repository docs and should not be assumed by reporters. If maintainers want a fully closed public security surface, that fallback must be published or verified separately.

Before Filing An Issue

  1. Read README.md.
  2. Read docs/README.md.
  3. Search existing issues and pull requests.