- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 21 for deletion (0.15 sec)
-
.cm/summary_table.cm
<td>{{ branch.diff.files_metadata | filter(attr='file', list=platform.subprojects) | map(attr='deletions') | sum }}</td> <td>{{ ((branch.diff.files_metadata | filter(attr='file', list=platform.subprojects) | map(attr='deletions') | sum) / (changes.additions + changes.deletions) * 100) | round(2) }}%</td>
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) -
.github/workflows/codeql-analysis.yml
matrix: # Override automatic language detection by changing the below list # Supported options are ['csharp', 'cpp', 'go', 'java', 'javascript', 'python'] language: ['java', 'javascript'] # Learn more... # https://docs.github.com/en/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#overriding-automatic-language-detection steps: - name: Checkout repository
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 4K bytes - Viewed (0) -
.cm/estimated_time_to_review.cm
# Each automation has an `if` key that defines conditions to run the automation, # as well as a `run` key with the actions to do. All the conditions need to be true # for the actions to run (there is an implicit AND relation between # the conditions on each line). Each condition is specified as a Jinja expression. You # can also use the constant `true` if you want to always run the actions.
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
# Each automation has an `if` key that defines conditions to run the automation, # as well as a `run` key with the actions to do. All the conditions need to be true # for the actions to run (there is an implicit AND relation between # the conditions on each line). Each condition is specified as a Jinja expression. You # can also use the constant `true` if you want to always run the actions.
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
# Each automation has an `if` key that defines conditions to run the automation, # as well as a `run` key with the actions to do. All the conditions need to be true # for the actions to run (there is an implicit AND relation between # the conditions on each line). Each condition is specified as a Jinja expression. You # can also use the constant `true` if you want to always run the actions.
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) -
.teamcity/src/main/kotlin/configurations/PerformanceTest.kt
} } failureConditions { // We have test-retry to handle the crash in tests javaCrash = false // We want to see the flaky tests for flakiness detection supportTestRetry = (performanceTestBuildSpec.type != PerformanceTestType.flakinessDetection) } if (testProjects.isNotEmpty()) { steps { preBuildSteps()
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 08:17:56 GMT 2024 - 5.3K bytes - Viewed (0) -
.cm/summary_table_platforms.cm
# Each automation has an `if` key that defines conditions to run the automation, # as well as a `run` key with the actions to do. All the conditions need to be true # for the actions to run (there is an implicit AND relation between # the conditions on each line). Each condition is specified as a Jinja expression. You # can also use the constant `true` if you want to always run the actions.
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/includes_todos.cm
# Each automation has an `if` key that defines conditions to run the automation, # as well as a `run` key with the actions to do. All the conditions need to be true # for the actions to run (there is an implicit AND relation between # the conditions on each line). Each condition is specified as a Jinja expression. You # can also use the constant `true` if you want to always run the actions.
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) -
build-logic/jvm/src/main/kotlin/gradlebuild.unittest-and-compile.gradle.kts
} } fun Project.isPerformanceProject() = setOf("build-scan-performance", "performance").contains(name) /** * Whether the project supports running with predictive test selection. * * Our performance tests don't work with PTS, yet. * Smoke and soak tests are hard to grasp for PTS, that is why we run them without.
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Wed Jan 17 13:36:27 GMT 2024 - 15.7K bytes - Viewed (0) -
.cm/code_experts.cm
# Each automation has an `if` key that defines conditions to run the automation, # as well as a `run` key with the actions to do. All the conditions need to be true # for the actions to run (there is an implicit AND relation between # the conditions on each line). Each condition is specified as a Jinja expression. You # can also use the constant `true` if you want to always run the actions.
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)