# Contributing

Thanks for your interest in dry-aged-deps. This guide covers how to contribute code, decisions, and bug reports.

## Before you start

- **Problems**: open an issue first using the **Report a problem** template under `.github/ISSUE_TEMPLATE/`. You do not need to pre-classify it as a bug or a feature -- this project practises ITIL problem management, so triage decides the category. Drive-by PRs without an issue are harder to merge because the problem framing is missing.
- **Security vulnerabilities**: do not open a public issue. See [SECURITY.md](SECURITY.md).
- **Usage questions**: use [Discussions](https://github.com/voder-ai/dry-aged-deps/discussions), not issues.

## Pull requests

1. **Branch off the default branch**.
2. **Make your change** with tests where applicable.
3. **Open the PR** with a clear description of what is changing and why.

### Commit style

- Follow Conventional Commits (`feat:`, `fix:`, `docs:`, `chore:`, etc.).
- Reference problem tickets in the commit message when the work closes one.
- Sign-off is not required.

## Code of conduct

Be kind. Engage in good faith. Critique ideas, not people. Maintainers reserve the right to lock or remove discussions, issues, or PRs that derail into personal attacks.

## License

By contributing, you agree your contributions are licensed under dry-aged-deps's license. See the project root for the canonical LICENSE file.

Copyright (c) 2026 the dry-aged-deps contributors.