- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 23 for Hevery (0.18 sec)
-
.cm/complex_changes.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # 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
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/add_usual_expert.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # 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
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/30_contributor_regression.yml
labels: [ "a:regression", "to-triage" ] assignees: [ ] body: - type: markdown attributes: value: | Please use our bug report template to report problems with something that has never worked. Regressions reports are greatly appreciated during our RC phase and before a final release. - type: textarea id: current-behavior attributes: label: Current Behavior
Others - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Feb 16 07:49:32 GMT 2024 - 2.7K bytes - Viewed (0) -
.cm/platform_labels.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # 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
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/estimated_time_to_review.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # 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
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/misc_labels.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # 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
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) -
.cm/summary_table.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # 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
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) -
.cm/lacks_tests.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # 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
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) -
.teamcity/src/main/kotlin/model/CIBuildModel.kt
// Include cross version tests, these take care of selecting a very small set of versions to cover when run as part of this stage, including the current version quick(true, true, true, 120, 4), // Include cross version tests, these take care of selecting a very small set of versions to cover when run as part of this stage, including the current version platform(true, true, true),
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Feb 23 01:54:48 GMT 2024 - 20.9K bytes - Viewed (0) -
.teamcity/src/test/kotlin/ApplyDefaultConfigurationTest.kt
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 08:17:56 GMT 2024 - 6.5K bytes - Viewed (0)