Search Options

Results per page
Sort
Preferred Languages
Advance

Results 11 - 17 of 17 for Group (0.15 sec)

  1. .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)
  2. .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)
  3. .cm/includes_todos.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 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)
  4. build-logic/buildquality/build.gradle.kts

        implementation(project(":binary-compatibility"))
    
        implementation("org.codenarc:CodeNarc") {
            exclude(group = "org.apache.groovy")
            exclude(group = "org.codehaus.groovy")
        }
        implementation("com.github.javaparser:javaparser-symbol-solver-core") {
            exclude(group = "com.google.guava")
        }
        implementation("org.gradle.kotlin:gradle-kotlin-dsl-conventions")
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Wed Apr 03 13:29:44 GMT 2024
    - 1.2K bytes
    - Viewed (0)
  5. build-logic/cleanup/src/main/java/gradlebuild/cleanup/services/KillLeakingJavaProcesses.java

                Matcher pidMatcher = pidPattern.matcher(line);
                if (commandLineArgsMatcher.find() && pidMatcher.find()) {
                    String pid = pidMatcher.group(1);
                    if (!MY_PID.equals(pid)) {
                        action.accept(pid, line);
                    }
                }
            });
        }
    
        private static List<String> ps() {
    Java
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 26 09:46:00 GMT 2024
    - 11.3K bytes
    - Viewed (0)
  6. .cm/code_experts.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:
    
      # Also post a comment that lists the best experts for the files that were modified.
    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)
  7. .cm/javadoc_on_new_files.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:
    
      javadoc_on_new_files:
        # Triggered for new Java files that lack Javadoc content.
        if:
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.8K bytes
    - Viewed (0)
Back to top