- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 23 for Automation (0.22 sec)
-
.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 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 1.7K bytes - Viewed (0) -
.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 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.7K bytes - Viewed (0) -
.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 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.1K bytes - Viewed (0) -
.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 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.1K bytes - Viewed (0) -
.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 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.2K bytes - Viewed (0) -
.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 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 6.5K bytes - Viewed (0) -
.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) -
.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
Plain Text - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 2.1K bytes - Viewed (0) -
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) -
.github/workflows/release-branch-cherrypick.yml
with: ref: ${{ github.event.inputs.release_branch }} - name: Get some helpful info for formatting id: cherrypick run: | git config --global user.name "TensorFlow Release Automation" git config --global user.email "******@****.***" git fetch origin master git cherry-pick ${{ github.event.inputs.git_commit }}
Others - Registered: Tue Apr 16 12:39:09 GMT 2024 - Last Modified: Tue Sep 12 14:49:29 GMT 2023 - 3.1K bytes - Viewed (0)