Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 28 for Automation (0.27 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 May 01 11:36:15 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 May 01 11:36:15 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 May 01 11:36:15 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 May 01 11:36:15 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 May 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.3K bytes
    - Viewed (0)
  6. .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 May 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  7. .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 May 01 11:36:15 GMT 2024
    - Last Modified: Mon Apr 22 15:32:31 GMT 2024
    - 2.5K 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 May 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 3K bytes
    - Viewed (0)
  9. .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)
  10. architecture-standards/0004-use-a-platform-architecture.md

    ### Platforms
    
    The platforms and their architecture modules are:
    
    #### Core automation platform
    
    This is a general purpose automation platform, which takes care of the efficient definition and execution of work, such as tasks.
    This platform is agnostic to what exactly the purpose of the work is.
    Plain Text
    - Registered: Wed Feb 14 11:36:15 GMT 2024
    - Last Modified: Wed Feb 07 00:56:13 GMT 2024
    - 4.5K bytes
    - Viewed (0)
Back to top