- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 18 for related (0.33 sec)
-
.cm/add_usual_expert.cm
# 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 someone is a primary author of the files in a change, but NOT the pr author, automatically add them as a reviewer.
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
# 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/lacks_tests.cm
# 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 lacks_tests: if:
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/estimated_time_to_review.cm
# 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 estimated_time_to_review:
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
# 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 %} platform_label_{{ platform.name }}:
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/summary_table_platforms.cm
# 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: - {{ ('summary_table_platforms' | isEnabledAutomation(pr)) }} run:
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
# 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 someone adds a TODO, remind them about it by requesting removal includes_todos: if:
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) -
.cm/misc_labels.cm
# 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: - {{ ('misc_labels' | isEnabledAutomation(pr)) }}
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) -
build-logic-commons/settings.gradle.kts
} // Shared basics for all include("basics") // Platform: defines shared dependency versions include("build-platform") // Compute the identity/version we are building and related details (like current git commit) include("module-identity") // Code quality rules common to :build-logic and the root build include("code-quality-rules") // Plugins to build :build-logic plugins
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Jan 12 16:22:45 GMT 2024 - 1.2K bytes - Viewed (0) -
architecture/standards/0002-avoid-using-java-serialization.md
- **Security:** Java serialization poses security risks, especially related to deserialization vulnerabilities. - **Version Compatibility:** With Java serialization, even minor changes to a class (like adding a field) can break compatibility. - **Cross-Language Compatibility:**
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu Feb 29 22:32:18 GMT 2024 - 2.3K bytes - Viewed (0)