Thanks for your interest in contributing!
- Be kind and respectful. (See CODE_OF_CONDUCT.md if present.)
- Discuss big changes via an issue before opening a PR.
- Keep PRs focused and small where possible.
- Requires: Xcode (latest), Swift 5.9+, macOS runner-compatible toolchain.
- Run tests with coverage:
swift test --enable-code-coverage
We use Conventional Commits to drive release notes and changelog entries:
feat: ...— new featurefix: ...— bug fixdocs: ...— documentation only changesrefactor: ...,perf: ...,test: ...,build: ...,ci: ..., etc.
Example:
feat(ui): add dark mode CSS variables
master— default, locked branch for stable history.
- feature/fix branches — open PRs into
master.
- Tests added/updated
- CI green
- Changelog updated (CHANGELOG.md under Unreleased)
- Docs/README updated if behavior changes
- Update
CHANGELOG.md(Unreleased → vX.Y.Z - YYYY-MM-DD) - Tag the release:
git tag -a vX.Y.Z -m "AuthPackage vX.Y.Z" git push origin refs/tags/vX.Y.Z - CI will publish artifacts and (if configured) create a GitHub Release.