Thank you for your interest in contributing to authkit. This guide covers questions, bug reports, feature requests, and pull requests. For private vulnerability reporting, use SECURITY.md instead of public channels.
Use GitHub Discussions for usage questions, troubleshooting, and general discussion.
Report non-security bugs through GitHub Issues. Include the following details when possible:
- version, commit, or environment details
- steps to reproduce
- expected behavior
- actual behavior
- logs, screenshots, or a minimal reproduction
If you are reporting a security issue, stop and follow SECURITY.md instead.
Use GitHub Discussions for feature requests and design proposals. For larger changes, describe the problem and a small proposed next step before starting implementation.
Contributors should:
- Keep changes focused and scoped to a single problem.
- Add or update tests when behavior changes.
- Update documentation when user-facing behavior changes.
- Describe the change clearly in the pull request.
- Make sure CI passes before requesting review.
Install the docs dependencies and run the repository checks:
npm --prefix docs install
moon ci --summary minimalUseful project commands:
moon run docs:build
moon run docs:start
moon run docs:typecheckKeep Go tests, linting, and docs checks passing together as the runtime packages grow.
Unless stated otherwise, contributions are accepted under the repository's dual license: Apache License 2.0 or MIT, at your option.