Thank you for taking the time to improve BoringCache.
- Use support@boringcache.com for account, workspace, billing, or product support.
- Report vulnerabilities privately according to the security policy.
- Use a repository issue for a reproducible bug, documentation correction, or focused feature proposal concerning that public repository.
Read the repository README before opening an issue or pull request. Some public repositories contain generated release artifacts or narrowly scoped distribution metadata; their files may not be the right place for a source change. For a non-trivial change, open an issue first so maintainers can confirm the correct boundary and avoid wasted work.
Please include:
- the BoringCache version or immutable Action/image reference;
- operating system, architecture, CI provider, and relevant tool versions;
- the command or minimal workflow that failed;
- expected and actual behavior; and
- scrubbed logs or diagnostics that help reproduce the problem.
Do not include access tokens, credentials, private repository content, customer data, or signed storage URLs.
Keep the change focused and explain the user-visible outcome. Add or update the smallest meaningful tests and documentation. Preserve generated-file and release boundaries described by the repository, and do not mix unrelated cleanup into the same change.
By contributing, you agree that your contribution is licensed under the license of the repository receiving it. Participation is governed by the BoringCache Code of Conduct.