- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 16 for costly (0.15 sec)
-
.cm/lacks_tests.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: # If a PR contains non-trivial source changes and no tests, add a comment to the PR
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2.4K bytes - Viewed (0) -
.cm/add_usual_expert.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.4K bytes - Viewed (0) -
.cm/complex_changes.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: # If a PR is very complex, require 2 approvals complex_changes: if:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.7K bytes - Viewed (0) -
architecture/build-state-model.md
The build session state also includes "cross session" state that is shared with any "nested" sessions that need to be created. This only happens when the `GradleBuild` task is used. You can mostly ignore the distinction between "cross session" and "build session" state. ### Build tree state "Build tree" is another name for the build definition.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun May 05 22:45:11 GMT 2024 - 3.4K bytes - Viewed (0) -
.teamcity/README.md
# CI Pipeline Configuration ## Open & import the project In your IDEA, `File` - `Open`, select `.teamcity/pom.xml`, `import as project`, and you'll have a Maven project. ## Project structure Mostly a standard Maven project structure. The entry point `settings.kts` defines the TeamCity project. There are 3 subprojects in the TeamCity project hierarchy: `Check` for Gradle builds, `Promotion` for releasing Gradle versions, `Util` for miscellaneous utilities.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Mar 06 23:02:25 GMT 2024 - 4K bytes - Viewed (0) -
README.md
**For more information, please visit the [official project homepage](https://gradle.org)** ## Getting Started
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun Mar 24 20:49:08 GMT 2024 - 3.9K bytes - Viewed (0) -
.cm/estimated_time_to_review.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 - 2K bytes - Viewed (0) -
.cm/platform_labels.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: # Label changes by affected platforms (in blue) {% for platform in platforms %}
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Apr 22 15:32:31 GMT 2024 - 2.5K bytes - Viewed (0) -
.cm/misc_labels.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 automations: # Add the a:documentation label to docs-only changes docs_only: if:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 3K bytes - Viewed (0) -
.cm/summary_table.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 automations: summary_table: if: - {{ is.requested or not pr.author_is_org_member }}
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)