- Sort Score
- Result 10 results
- Languages All
Results 1 - 9 of 9 for Command (0.22 sec)
-
.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 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
# 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 01 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 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
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 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 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 01 11:36:15 GMT 2024 - Last Modified: Tue Feb 13 13:53:39 GMT 2024 - 4.9K bytes - Viewed (2) -
.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 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2.4K bytes - Viewed (0) -
build-logic-commons/basics/src/main/kotlin/gradlebuild/basics/BuildEnvironment.kt
else -> parent.parentOrRoot() } } fun Project.releasedVersionsFile() = repoRoot().file("released-versions.json") /** * We use command line Git instead of JGit, because JGit's `Repository.resolve` does not work with worktrees. */
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Feb 09 22:52:01 GMT 2024 - 5.7K bytes - Viewed (2) -
.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 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.9K bytes - Viewed (0) -
CONTRIBUTING.md
This may help you better understand and contribute to Gradle. ### Debugging Gradle You can debug Gradle by adding `-Dorg.gradle.debug=true` to the command-line. Gradle will wait for you to attach a debugger at `localhost:5005` by default. If you made changes to build logic in the `build-logic` included build, you can run its tests by executing `./gradlew :build-logic:check`.
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Feb 09 15:30:53 GMT 2024 - 15.6K bytes - Viewed (0)