Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 21 for relation (0.18 sec)

  1. .cm/add_usual_expert.cm

    # Each automation has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    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 has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    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/estimated_time_to_review.cm

    # Each automation has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    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)
  4. .cm/platform_labels.cm

    # Each automation has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    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)
  5. .cm/misc_labels.cm

    # Each automation has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    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)
  6. .cm/summary_table.cm

    # Each automation has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    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)
  7. .cm/lacks_tests.cm

    # Each automation has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    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)
  8. .cm/summary_table_platforms.cm

    # Each automation has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    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)
  9. .cm/includes_todos.cm

    # Each automation has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    Plain Text
    - Registered: Wed May 01 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.9K bytes
    - Viewed (0)
  10. .cm/code_experts.cm

    # Each automation has an `if` key that defines conditions to run the automation,
    # as well as a `run` key with the actions to do. All the conditions need to be true
    # for the actions to run (there is an implicit AND relation between
    # the conditions on each line).  Each condition is specified as a Jinja expression.  You
    # can also use the constant `true` if you want to always run the actions.
    
    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)
Back to top