Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 182 for automation (0.19 sec)

  1. .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
    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)
  2. .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
    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)
  3. .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
    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)
  4. .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
    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)
  5. .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
    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. .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
    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)
  7. .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
    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)
  8. .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
    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)
  9. .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.
    JavaScript
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 3.1K bytes
    - Viewed (0)
  10. .cm/summary_table.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
    Plain Text
    - Registered: Wed Apr 17 11:36:08 GMT 2024
    - Last Modified: Thu Feb 08 15:20:44 GMT 2024
    - 6.5K bytes
    - Viewed (0)
Back to top