# Contributing to the Gradle Build Tool

Thank you for your interest in contributing to Gradle!
This guide explains how to contribute to the core Gradle components, 
extensions and documentation located in this repository.
For other extensions and components, see the 
[Gradle Community Resources](https://gradle.org/resources/).

This guide will help you to...

* maximize the chance of your changes being accepted
* work on the Gradle code base

Contributing as part of a class
-------------------------------
In general Elasticsearch is happy to accept contributions that were created as
part of a class but strongly advise against making the contribution as part of
the class. So if you have code you wrote for a class feel free to submit it.

Please, please, please do not assign contributing to Elasticsearch as part of a

# Contributing guidelines

## Pull Request Checklist

Before sending your pull requests, make sure you do the following:

-   Read the [contributing guidelines](CONTRIBUTING.md).
-   Read the [Code of Conduct](CODE_OF_CONDUCT.md).
-   Ensure you have signed the
    [Contributor License Agreement (CLA)](https://cla.developers.google.com/).
-   Check if your changes are consistent with the

# Development - Contributing

First, you might want to see the basic ways to [help FastAPI and get help](help-fastapi.md).

## Developing

If you already cloned the [fastapi repository](https://github.com/fastapi/fastapi) and you want to deep dive in the code, here are some guidelines to set up your environment.

### Install requirements

Create a virtual environment and install the required packages with [`uv`](https://github.com/astral-sh/uv):

    .converter("dateField", new DateConverter("yyyy-MM-dd"));

BeanUtil.copyBeanToBean(source, dest, options);
```

## 🤝 Contributing

We welcome contributions! Please see our contributing guidelines for details.

### Development Workflow
1. **Fork** the repository on GitHub
2. **Create** your feature branch: `git checkout -b feature/amazing-feature`

.github/ISSUE_TEMPLATE                  @gradle/bt-product-operations
LICENSE                                 @gradle/bt-product-operations
*.md                                    @gradle/bt-product-operations @gradle/bt-docs-reviewers
contributing/                           @gradle/bt-product-operations @gradle/bt-docs-reviewers

# Cross-cutting architecture checks and decisions
.github/CODEOWNERS                          @gradle/bt-architecture-council

   (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
   SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

CONTRIBUTION AGREEMENT

By contributing to the BVLC/caffe repository through pull-request, comment,
or otherwise, the contributor releases their content to the

* Затем добавьте комментарий, что Вы попробовали, чтобы я знал, что Вы это проверили. 🤓

## Создать пулл-реквест { #create-a-pull-request }

Вы можете [сделать вклад](contributing.md) в исходный код пулл-реквестами, например:

* Исправить опечатку, найденную в документации.

* Ayrıca neleri denediğinizi yorumlara yazın; böylece kontrol ettiğinizi anlarım. 🤓

## Pull Request Oluşturun { #create-a-pull-request }

Örneğin şunlar için Pull Request'lerle kaynak koda [katkıda bulunabilirsiniz](contributing.md):

* Dokümantasyonda bulduğunuz bir yazım hatasını düzeltmek.

## Einen Pull Request erstellen { #create-a-pull-request }

Sie können [zum Quellcode mit Pull Requests beitragen](contributing.md), zum Beispiel:

* Um einen Tippfehler zu beheben, den Sie in der Dokumentation gefunden haben.