- Sort Score
- Result 10 results
- Languages All
Results 11 - 18 of 18 for Jeep (0.13 sec)
-
.cm/summary_table_platforms.cm
# 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 - comment_added automations: summary_table_platforms: if:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0) -
architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md
When the Kotlin DSL was introduced, we made an effort to add non-Groovy equivalents for all APIs. This has been mostly done, but there remain a few holdouts (fixing these is out of scope). To keep the Groovy DSL ergonomic, we generate methods as necessary from the non-Groovy equivalents. Doing this provides the following specific benefits: - **Reduce the API surface** - We no longer need to maintain two methods.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Mar 10 20:38:06 GMT 2024 - 1.8K bytes - Viewed (0) -
.cm/includes_todos.cm
# 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 - comment_added automations:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.9K bytes - Viewed (0) -
CONTRIBUTING.md
* Keep commits discrete. Avoid including multiple unrelated changes in a single commit. * Keep commits self-contained. Avoid spreading a single change across multiple commits. A single commit should make sense in isolation. ### Testing changes
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat May 04 07:43:02 GMT 2024 - 15.6K bytes - Viewed (0) -
architecture/standards/README.md
For now we just have this global repository of ADRs. If we see fit, we can break these out to per-platform ones, or keep a hybrid approach to having global and platform-specific ADSs. Our aim is to keep the process lightweight and approachable.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Feb 21 06:30:44 GMT 2024 - 546 bytes - Viewed (0) -
.cm/code_experts.cm
# 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 - comment_added automations:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.3K bytes - Viewed (0) -
.cm/javadoc_on_new_files.cm
# 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 - comment_added automations: javadoc_on_new_files:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.8K bytes - Viewed (0) -
build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/upgrades/UpgradedProperties.java
* - A return type is changed for a getter `getX` of an upgraded property * * We don't automatically accept changes when the @since annotation is missing, because we want to keep this information on the API. */ public static boolean shouldAcceptForUpgradedProperty(JApiMethod jApiMethod, Violation violation, ViolationCheckContext context) {
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Apr 23 08:40:36 GMT 2024 - 6.8K bytes - Viewed (0)