"path": "platforms/jvm/distributions-jvm",
    "unitTests": false,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "distributions-native",
    "path": "platforms/native/distributions-native",
    "unitTests": false,
    "functionalTests": false,
    "crossVersionTests": false
  },
  {
    "name": "distributions-publishing",

        Please open IntelliJ-related issues on [the JetBrains Issue Tracker](https://youtrack.jetbrains.com/newIssue?project=IDEA)
        Please open Gradle Native-related issues on [the Gradle Native repository](https://github.com/gradle/gradle-native/issues)

        Provide a brief summary of the issue in the title above
  - type: textarea
    id: expected-behavior
    attributes:
      label: Expected Behavior

            <option value="$PROJECT_DIR$/platforms/native/distributions-native" />
            <option value="$PROJECT_DIR$/platforms/native/language-native" />
            <option value="$PROJECT_DIR$/platforms/native/platform-native" />
            <option value="$PROJECT_DIR$/platforms/native/testing-native" />
            <option value="$PROJECT_DIR$/platforms/native/tooling-native" />

          cache: 'gradle'
          native-image-job-reports: true

      - name: Setup Gradle
        uses: gradle/actions/setup-gradle@v5

      - name: Build okcurl
        run: ./gradlew okcurl:nativeBuild

      - name: Setup Gradle
        uses: gradle/actions/setup-gradle@v5

      - name: Run native-image tests
        run: ./gradlew -PgraalBuild=true native-image-tests:nativeTest

  testandroid:

      "coverage" : {
        "per_day" : [ "linux" ]
      }
    } ]
  }, {
    "testId" : "org.gradle.performance.regression.buildcache.TaskOutputCachingNativePerformanceTest.clean assemble with local cache (native project)",
    "groups" : [ {
      "testProject" : "bigCppApp",
      "coverage" : {
        "per_day" : [ "linux" ]
      }
    }, {
      "testProject" : "bigCppMulti",
      "coverage" : {

        <include>*.java</include>
      </includes>
      <lineEnding>dos</lineEnding>
    </fileSet>
    <fileSet>
      <directory>target/dependency/org/jline/nativ</directory>
      <outputDirectory>lib/jline-native</outputDirectory>
      <includes>
        <include>**/*.so</include>
        <include>**/*.jnilib</include>
        <include>**/*.dll</include>
      </includes>
    </fileSet>
	<fileSet>

* **Inconsistent API surface**: Public APIs with mixed spelling conventions appear less professional and polished
* **Harder for non-native speakers**: Contributors and users for whom English is a second language benefit from a single, consistent convention

Once a native speaker comes, reviews the PR, and approves it, the GitHub Action will come and remove the `awaiting-review` label, and add the `approved-1` label.

This way, we can notice when there are new translations ready, because they have the `approved-1` label.

## Merge Translation PRs

    # Messages to create or check
    new_translation_message = f"Good news everyone! 😉 There's a new translation PR to be reviewed: #{pr.number} by @{pr.user.login}. 🎉 This requires 2 approvals from native speakers to be merged. 🤓"
    done_translation_message = f"~There's a new translation PR to be reviewed: #{pr.number} by @{pr.user.login}~ Good job! This is done. 🍰☕"

    # Normally only one language, but still

    the implementation trade-offs. We can't use our HTTP client engine on Kotlin/JS, and we weren't
    prepared to build a TLS API for Kotlin/Native.

    We'd prefer a multiplatform HTTP client API that's backed by OkHttp on Android and JVM, and
    other engines on other platforms. [Ktor] does this pretty well today!