# Contributing to fapilog

Thank you for your interest in contributing to fapilog! We welcome contributions of all kinds.

## Contributing Guide

For detailed information about contributing to fapilog, including:

- **Development setup** - How to set up your local environment
- **Development workflow** - Branch strategy and development process
- **Code quality standards** - Linting, testing, and type checking
- **Commit and PR guidelines** - Conventional commits and pull request process
- **Release process** - How releases are made and versioned

Please see our comprehensive **[Contributing Guide](https://github.com/chris-haste/fapilog/blob/main/CONTRIBUTING.md)** in the repository root.

```{toctree}
:maxdepth: 1
:hidden:

test-categories
contract-tests
configuration-parity
changelog
```

## Quick Links

- **[Report a Bug](https://github.com/chris-haste/fapilog/issues/new?labels=bug)** - Found an issue? Let us know
- **[Request a Feature](https://github.com/chris-haste/fapilog/issues/new?labels=enhancement)** - Have an idea? Share it
- **[Ask a Question](https://github.com/chris-haste/fapilog/discussions)** - Need help? Start a discussion
- **[Test Categories](test-categories.md)** - Test markers and CI subsets
- **[Contract Tests](contract-tests.md)** - Schema compatibility testing patterns
- **[Configuration Parity](configuration-parity.md)** - Settings/Builder API alignment

## Key Development Commands

```bash
# Install development dependencies
pip install -e ".[dev]"

# Run tests
hatch run test

# Run linting
hatch run lint

# Run type checking
hatch run typecheck

# Run tests with coverage
hatch run test-cov
```

## Code of Conduct

We are committed to providing a welcoming and inclusive environment. Please be respectful and professional in all interactions.

---

_Your contributions help make fapilog better for everyone. Thank you for being part of our community!_
