# Contributing to Freelens

Thank you for considering contributing to Freelens! We value your support and
are open to collaboration. Here are some guidelines to help you get started.

## How to Contribute

### Reporting Issues

If you find a bug or have a feature request, please check the [existing
issues](https://github.com/freelensapp/freelens/issues) to see if it has
already been reported. If not, you can create a new issue. Please provide as
much detail as possible, including:

- Steps to reproduce the issue
- Your environment (OS, Freelens version, installation method)

### Submitting Pull Requests

1. Fork the repository.
2. Create a new branch for your feature or bugfix (`git checkout -b feature-name`).
3. Make your changes.
4. Test your changes thoroughly.
5. Commit your changes (`git commit -m 'Add some feature'`).
6. Push to the branch (`git push origin feature-name`).
7. Create a pull request.

Please ensure your pull request adheres to the following guidelines:

- Describe the purpose of the pull request.
- Reference any related issues.
- Ensure all tests pass.
- Follow the coding standards described in the [Style Guides](#style-guides) section.

## Development Environment Setup

Visit [Development](https://github.com/freelensapp/freelens/wiki/Development)
wiki page to see how to build the application from source.

Learn about the project from the
[DeepWiki](https://deepwiki.com/freelensapp/freelens) documentation.

## Style Guides

### Code Style

- Follow the existing coding style.
- Use [Biome](https://biomejs.dev/) to lint and format your code.
- Verify your changes with [Trunk Check](https://docs.trunk.io/cli).

### Commit Messages

- Write clear and descriptive commit messages.
- Reference related issues or pull requests when applicable.

## Community

Join our [Discussions](https://github.com/freelensapp/freelens/discussions)
for general questions and community support.