Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 115 for Every (0.14 sec)

  2. github.com/gradle/gradle

    .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 2.4K bytes
    - Viewed (0)
  3. github.com/gradle/gradle

    .cm/javadoc_on_new_files.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 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  4. github.com/gradle/gradle

    .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 3K bytes
    - Viewed (0)
  5. github.com/gradle/gradle

    .cm/code_experts.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 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.3K bytes
    - Viewed (0)
  6. github.com/gradle/gradle

    .cm/summary_table_platforms.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 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.4K bytes
    - Viewed (0)
  7. github.com/gradle/gradle

    .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.7K bytes
    - Viewed (0)
  8. github.com/gradle/gradle

    .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.4K bytes
    - Viewed (0)
  9. github.com/gradle/gradle

    .cm/includes_todos.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 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.9K bytes
    - Viewed (0)
  10. github.com/gradle/gradle

    .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 2K bytes
    - Viewed (0)
  11. github.com/gradle/gradle

    .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Mon Apr 22 15:32:31 GMT 2024
    - 2.5K bytes
    - Viewed (0)
Back to top