This is the organization-wide default support guide for repositories
under the blackoutsecure GitHub organization. Repositories may add
their own SUPPORT.md with project-specific channels or service
levels — when present, the repo's own copy overrides this one.
- Start with the affected repository's
README.mdfor setup and usage guidance. - Search existing issues and discussions before opening a new one.
- Open a regular issue using the default templates for bug reports or feature requests.
- For security concerns, follow the process in SECURITY.md (private channels only — never a public issue).
- Repository, version, or commit SHA you're running.
- A clear description of the problem or request.
- Steps to reproduce or expected vs. actual behavior.
- Environment details (OS, language runtime, relevant tool versions).
- Relevant logs or output — redact secrets, tokens, customer data, and PII.
- Links to related issues, PRs, or external references.
- Clarifying intended behavior or design.
- Investigating suspected defects with a clear reproduction.
- Reviewing proposed changes via pull request.
- Password resets, account recovery, or identity provider issues.
- Production operations owned by third parties (cloud vendors, hosting providers, downstream forks we do not maintain).
- One-on-one consulting outside the scope of the open-source project.
Response times are best-effort for community issues; we do not
promise a service-level agreement unless one is explicitly stated in
a repository's own SUPPORT.md.