- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 16 for checker (0.17 sec)
-
build-logic-commons/code-quality-rules/src/main/resources/checkstyle/checkstyle-groovy.xml
~ See the License for the specific language governing permissions and ~ limitations under the License. --> <!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd"> <module name="Checker"> <module name="SuppressionFilter"> <property name="file" value="${config_loc}/suppressions.xml"/> </module> <module name="RegexpHeader">
XML - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Wed Dec 09 08:14:05 GMT 2020 - 1.4K bytes - Viewed (0) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/FindBrokenInternalLinks.java
Java - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Wed Apr 05 07:57:56 GMT 2023 - 8.6K bytes - Viewed (0) -
build-logic-commons/code-quality-rules/src/main/resources/checkstyle/checkstyle.xml
~ See the License for the specific language governing permissions and ~ limitations under the License. --> <!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd"> <module name="Checker"> <module name="SuppressionFilter"> <property name="file" value="${config_loc}/suppressions.xml"/> </module>
XML - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Dec 16 22:05:16 GMT 2022 - 6.3K bytes - Viewed (0) -
build-logic-commons/code-quality-rules/src/main/resources/checkstyle/checkstyle-api.xml
~ See the License for the specific language governing permissions and ~ limitations under the License. --> <!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd"> <module name="Checker"> <module name="SuppressionFilter"> <property name="file" value="${config_loc}/suppressions.xml"/> </module> <module name="JavadocPackage"/>
XML - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Nov 17 23:20:14 GMT 2022 - 1.6K bytes - Viewed (0) -
.cm/lacks_tests.cm
# can also use the constant `true` if you want to always run the actions. # 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
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/add_usual_expert.cm
# can also use the constant `true` if you want to always run the actions. # 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
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
# can also use the constant `true` if you want to always run the actions. # 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
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/estimated_time_to_review.cm
# can also use the constant `true` if you want to always run the actions. # 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
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
# can also use the constant `true` if you want to always run the actions. # 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
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
# can also use the constant `true` if you want to always run the actions. # 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
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)