- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 12 for Command (0.57 sec)
-
.cm/lacks_tests.cm
# To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # This section could also appear ahead of the automations section. colors: yellow: 'ffb300' includes_src_changes: {{ files | match(regex=r/.*\/src\//) | some }}
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/complex_changes.cm
approvals: 2 # To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # This section could also appear ahead of the automations section.
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/README.md
## Gradle runtimes Gradle is also made up of several different processes that work together to "run the build", such as the Gradle daemon and the `gradlew` command. Each process, or "runtime", applies different constraints to the code that runs in that process. For example, each process has different supported JVMs and a different set of services available for dependency injection.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 2.4K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/30_contributor_regression.yml
validations: required: true - type: input id: build-scan-url attributes: label: Build scan URL (optional) description: | You can run your build command with `--scan` to publish a Build Scan to [scans.gradle.com](https://scans.gradle.com/). validations: required: false - type: textarea id: environment attributes:
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Feb 16 07:49:32 GMT 2024 - 2.7K bytes - Viewed (0) -
.cm/estimated_time_to_review.cm
# To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # This section could also appear ahead of the automations section. # This function calculates the estimated time to review and makes it available in the automation above.
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
{% endfor %} # To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # TODO: It would be very nice to avoid having this list somehow, but it needs to be defined in YAML and not in JS for the looping template to work
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
color: 'E94637' # To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # The results of these calculations are assigned to `is.formatting`, `is.docs` and `is.tests`. is: formatting: {{ source.diff.files | isFormattingChange }}
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/includes_todos.cm
# To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # This section could also appear ahead of the automations section. colors:
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) -
.github/ISSUE_TEMPLATE/10_contributor_bug_report.yml
validations: required: true - type: input id: build-scan-url attributes: label: Build scan URL (optional) description: | You can run your build command with `--scan` to publish a Build Scan to [scans.gradle.com](https://scans.gradle.com/). validations: required: false - type: textarea id: environment attributes:
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Feb 16 07:49:32 GMT 2024 - 3K bytes - Viewed (0) -
.teamcity/src/main/kotlin/util/AdHocPerformanceScenario.kt
fun ParametrizedWithType.profilerParam(defaultProfiler: String) { text( "profiler", defaultProfiler, display = ParameterDisplay.PROMPT, allowEmpty = false, description = "Command line option for the performance test task to enable profiling. For example `async-profiler`, `async-profiler-heap`, `async-profiler-all` or `jfr`. Use `none` for benchmarking only." ) }
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Feb 13 13:53:39 GMT 2024 - 4.9K bytes - Viewed (2)