3. **A relationship, not a transaction.** We view community PRs as an important part of our relationship with the Gradle community. We hope contributors will learn from the review process, stay engaged, and continue helping us build Gradle.

## In summary

We welcome AI-assisted contributions from people who understand what they're submitting and are ready to collaborate on it.

/// tip

This is the ultimate **vibe-driven development** experience. You don't need to think about what your API does, just let the LLM handle it. 🧘

///

## Try It { #try-it }

Go ahead, try it:

{* ../../docs_src/vibe/tutorial001_py310.py *}

  public void testConstraint() {
    /*
     * We'll give ourselves a pass on testing all the possible ways of breaking the constraint,
     * because we know that newClassMap() is implemented using ConstrainedMap which is itself
     * well-tested. A purist would object to this, but what can I say, we're dirty cheaters.
     */
    map.put(Integer.class, new Integer(5));

* Why is this change done? What's the use case?
* For user-facing features, what will the API look like?
* What test cases should it have? What could go wrong?
* How will it roughly be implemented? We'll happily provide code pointers to save you time.

We may ask you to answer these questions directly in the GitHub issue or (for large changes) in a shared Google Doc.

* `feature`: Features
    * New features, adding support for things that didn't exist before.
* `bug`: Fixes

- [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
- [ ] Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
- [ ] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.

        requirements {
            requiresNotSharedHost()
        }

    /*
     To avoid unnecessary rerun, what we do here is a bit complicated:

     1. Build a Gradle distribution with a fixed timestamp and hash it, but never use this distribution.

    suite.addTestSuite(ImmutableClassToInstanceMapTest.class);

    suite.addTest(
        MapTestSuiteBuilder.using(
                new TestClassToInstanceMapGenerator() {
                  // Other tests will verify what real, warning-free usage looks like
                  // but here we have to do some serious fudging
                  @Override
                  @SuppressWarnings({"unchecked", "rawtypes"})

    steps:
      - name: git clone
        uses: actions/checkout@v6
      - name: setup java
        uses: actions/setup-java@v5
        with:
          distribution: microsoft #because that's what is available on ARM windows. zulu would also be an option.
          java-version: 17
      - uses: actions/download-artifact@v8
        with:
          name: build-receipt.properties

bazel_dep(name = "zstd", version = "1.5.7", repo_name = "net_zstd")
bazel_dep(name = "pybind11_bazel", version = "2.13.6")
bazel_dep(name = "pybind11_protobuf", version = "0.0.0-20250210-f02a2b7")

# NOTE: This is a newer version compared to what was used in WORKSPACE
# and it breaks wheel tests.
# TODO: Fix the incompatibility with wheel tests.
bazel_dep(name = "pybind11_abseil", version = "202402.0")