# Contributing to TimeTracker

Thank you for your interest in contributing to TimeTracker. This page gives you a quick overview; full guidelines are in the developer documentation.

## How to Contribute

- **Report bugs** — Use the [GitHub issue tracker](https://github.com/drytrix/TimeTracker/issues). Include steps to reproduce, expected vs actual behavior, and your environment (OS, deployment method, version).
- **Improve translations (no Git)** — Use the **Translation improvement** issue template, translate on **[Crowdin (Drytrix TimeTracker)](https://crowdin.com/project/drytrix-timetracker)**, or read [docs/CONTRIBUTING_TRANSLATIONS.md](docs/CONTRIBUTING_TRANSLATIONS.md) for spreadsheet, maintainer workflow, and Crowdin setup ([`crowdin.yml`](crowdin.yml), **Actions → Crowdin sync**).
- **Suggest features** — Open a [feature request](https://github.com/drytrix/TimeTracker/issues/new?template=feature_request.md) with a clear description and use case.
- **Submit code** — Fork the repo, create a branch, make your changes, add tests, and open a pull request. Follow the [full contributing guidelines](docs/development/CONTRIBUTING.md) for setup, coding standards, and PR process.

## Full Guidelines

For development setup, coding standards, testing, pull request process, and commit conventions, see:

- **[Contributor Guide](docs/development/CONTRIBUTOR_GUIDE.md)** — Architecture, local dev, testing, how to add routes/services/templates, versioning
- **[Contributing guidelines (full)](docs/development/CONTRIBUTING.md)** — Development setup, coding standards, testing, PR process
- **[Code of Conduct](docs/development/CODE_OF_CONDUCT.md)** — Community standards and expected behavior
- **[CHANGELOG.md](CHANGELOG.md)** — How we track changes; update the *Unreleased* section for user-facing changes

## License

By contributing, you agree that your contributions will be licensed under the [GNU General Public License v3.0](LICENSE) used by this project.