- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 25 for itos (0.17 sec)
-
.cm/add_usual_expert.cm
# 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 # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit
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) -
.cm/complex_changes.cm
# 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 # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit
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) -
.cm/estimated_time_to_review.cm
# 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 # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit
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
# 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 # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit
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) -
.cm/misc_labels.cm
# 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 # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 3K bytes - Viewed (0) -
.cm/summary_table.cm
# 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 # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit
Plain Text - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 6.5K bytes - Viewed (0) -
.teamcity/src/main/kotlin/model/bucket-extensions.kt
* if some elements are too small, they will be aggregated by smallElementAggregateFunction. * * @param list the list to split, must be ordered by size desc * @param toIntFunction the function used to map the element to its "size" * @param largeElementSplitFunction the function used to further split the large element into smaller pieces * @param smallElementAggregateFunction the function used to aggregate tiny elements into a large bucket
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Nov 17 05:17:44 GMT 2022 - 4K bytes - Viewed (0) -
architecture-standards/0002-avoid-using-java-serialization.md
## Date 2012-12-01 ## Context In Gradle, we often need to serialize in-memory objects for caching or transmitting them across process barriers, etc. Java serialization is one way to implement this, however, despite its simplicity of implementation, it has several drawbacks:
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Thu Feb 08 21:48:27 GMT 2024 - 1.9K bytes - Viewed (0) -
.cm/lacks_tests.cm
# 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 # within the file. We keep each automation (or very closely related group of automations) in # its own file. on: - pr_created - commit
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2.4K bytes - Viewed (0) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/GradleKotlinDslRuntimeGeneratedSources.java
* This is not correct as it should do this with the built distribution instead. * * Doing it correctly would require running a Gradle build with the full * distribution and extracting the generated api jar from its Gradle user home, * slowing down building documentation. * * All this would be so much simpler if the Kotlin extensions to the Gradle API * were generated at build time instead. *
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Sun Mar 19 17:15:23 GMT 2023 - 3.9K bytes - Viewed (0)