KofTwentyTwo/ci-policy: ci / fork-guard (push) Skipped
KofTwentyTwo/ci-policy: ci / gradle-0 (push) Skipped
KofTwentyTwo/ci-policy: ci / manifests-1 (push) Skipped
KofTwentyTwo/ci-policy: ci / rust-2 (push) Skipped
KofTwentyTwo/ci-policy: ci / rust-3 (push) Skipped
KofTwentyTwo/ci-policy: ci / not-enrolled (push) Skipped
KofTwentyTwo/ci-policy: Shared source and config CI / gate (push) Canceled after 0s
KofTwentyTwo/ci-policy: Shared source and config CI / secrets (push) Canceled after 0s
KofTwentyTwo/ci-policy: Shared source and config CI / verify (push) Canceled after 0s
KofTwentyTwo/ci-policy: ci / source-config-4 (push) Canceled after 0s
KofTwentyTwo/ci-policy: ci / ci-result (push) Canceled after 0s
Code of conduct, support guide, and account profile inherited by every KofTwentyTwo repository (K22-REPO-10). Tracked on KofTwentyTwo/gclo#66. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>
933 B
933 B
Support
Thanks for using a KofTwentyTwo project. Here is where to go for help.
| Need | Where |
|---|---|
| A question, a how-to, or an idea | The repository's Discussions tab (https://github.com/KofTwentyTwo/<repo>/discussions) |
| A bug or a concrete change request | The repository's Issues tab, using the issue templates |
| A security vulnerability | Not an issue or discussion. Use the repository's Security tab, then Report a vulnerability (private vulnerability reporting); each repository's SECURITY.md has the details and timelines |
| A code of conduct concern | See CODE_OF_CONDUCT.md |
Before opening anything, search the existing issues and discussions: the answer is often already there.
These are personal open-source projects maintained in spare time. Issues and discussions are read regularly, but there is no guaranteed response time outside the security process.