- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 42 for have (0.14 sec)
-
architecture-standards/0003-avoid-introducing-Groovy-types-to-public-api.md
Doing this provides the following specific benefits: - **Reduce the API surface** - We no longer need to maintain two methods. - **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL. - **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages. ## Decision
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Wed Jan 31 14:32:10 GMT 2024 - 1.8K bytes - Viewed (0) -
.github/workflows/pull-metadata.yml
on: pull_request_target: types: [ closed ] jobs: check_pull_metadata: runs-on: ubuntu-latest permissions: issues: write pull-requests: write steps: # Check that PRs have proper metadata: labels and milestone # https://github.com/gradle/issue-management-action/blob/main/src/pull-metadata.ts - uses: gradle/issue-management-action@v1 with:
Others - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon Jan 22 06:29:03 GMT 2024 - 460 bytes - Viewed (0) -
.cm/add_usual_expert.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0) -
Development.md
2. That should be it. The suggestion will be displayed in the "Try" section. ### Remove generic suggestions For some scenarios, it doesn't make sense to display all the generic suggestions we currently have. E.g. `--stacktrace` for a compilation error is not helpful. To influence the generic suggestions Gradle displays, the NonGradleCause interface was introduced.
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Feb 06 22:54:40 GMT 2024 - 1.8K bytes - Viewed (0) -
.cm/complex_changes.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.7K bytes - Viewed (0) -
build-logic-commons/gradle-plugin/src/main/kotlin/gradlebuild.code-quality.gradle.kts
"JdkObsolete", // Most of the checks are good, but we do not want to replace all LinkedLists without a good reason // NEVER "MissingSummary", // We have another mechanism to check Javadocs on public API "InjectOnConstructorOfAbstractClass", // We use abstract injection as a pattern "JavaxInjectOnAbstractMethod", // We use abstract injection as a pattern
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Jan 30 10:26:21 GMT 2024 - 6K bytes - Viewed (0) -
.teamcity/src/main/kotlin/model/FunctionalTestBucketGenerator.kt
parallelization: (Int) -> ParallelizationMethod ): List<SmallSubprojectBucket> { // splitIntoBuckets() method expects us to split large element into N elements, // but we want to have a single bucket with N batches. // As a workaround, we repeat the bucket N times, and deduplicate the result at the end val resultIncludingDuplicates = splitIntoBuckets(
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Feb 15 17:04:41 GMT 2024 - 8.5K bytes - Viewed (0) -
.github/workflows/issue-metadata.yml
on: issues: types: [ opened, unlabeled, closed ] jobs: check_issue_metadata: runs-on: ubuntu-latest permissions: issues: write steps: # Check that issues have proper metadata: labels and milestone # https://github.com/gradle/issue-management-action/blob/main/src/issue-metadata.ts - uses: gradle/issue-management-action@v1 with:
Others - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon Jan 22 06:29:03 GMT 2024 - 446 bytes - Viewed (0) -
.cm/estimated_time_to_review.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2K bytes - Viewed (0) -
.cm/platform_labels.cm
# can also use the constant `true` if you want to always run the actions. # Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon Apr 22 15:32:31 GMT 2024 - 2.5K bytes - Viewed (0)