- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 15 for redhated (0.22 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) -
.github/CODEOWNERS
## ## CODEOWNERS style rules: ## 1. Prefer team ownership over individual user ownership. ## 2. GBT-related team should be listed first. ## 3. Try to keep paths alphabetically sorted within visual groups. ## 4. List individual owners last. ## # bt-unassigned-maintainers must be the first owner
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 15:52:09 GMT 2024 - 9.8K 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) -
.cm/plugins/filters/isEnabledAutomation/index.js
* </ul> * * @param {string} automationName - The automation name (*.cm file name containing the automation) to check. * @param {Map} pr - The gitStream PR instance to check (includes metadata related to the pull request). * @returns {boolean} Returns true if the outlined conditions are met, otherwise false. * @example {{ 'platform_labels' | isEnabledAutomation(pr) }} */ function isEnabledAutomation(automationName, pr) {
JavaScript - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 3.1K 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: # Add a label that indicates how many minutes it will take to review the PR and categorizes it
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) -
.github/ISSUE_TEMPLATE/10_contributor_bug_report.yml
Please open Android-related issues on [the Android Issue Tracker](https://source.android.com/source/report-bugs) Please open IntelliJ-related issues on [the JetBrains Issue Tracker](https://youtrack.jetbrains.com/newIssue?project=IDEA) Please open Gradle Native-related issues on [the Gradle Native repository](https://github.com/gradle/gradle-native/issues)
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Feb 16 07:49:32 GMT 2024 - 3K bytes - Viewed (0) -
.cm/summary_table_platforms.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: summary_table_platforms: if:
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)