- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 26 for Every (0.16 sec)
-
.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 May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2.4K bytes - Viewed (0) -
.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 May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.7K bytes - Viewed (0) -
.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 May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.4K bytes - Viewed (0) -
.teamcity/src/test/kotlin/ApplyDefaultConfigurationTest.kt
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 08:17:56 GMT 2024 - 6.5K bytes - Viewed (0) -
architecture/build-state-model.md
## Composition by architecture modules Each [architecture module and platform](platforms.md) can contribute code to any of the elements. Not every module contributes to every element.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sun May 05 22:45:11 GMT 2024 - 3.4K bytes - Viewed (0) -
.github/workflows/team-triage-stale.yml
name: 'Requeue stale team-triage items' on: schedule: # Execute every day at 00:05 to avoid conflicts with other workflows - cron: '5 0 * * *' permissions: {} jobs: requeue: permissions: issues: write pull-requests: write runs-on: ubuntu-latest steps: - uses: actions/stale@v9 with: operations-per-run: 50 remove-stale-when-updated: false
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 835 bytes - Viewed (0) -
build-logic/documentation/src/main/groovy/gradlebuild/docs/dsl/source/ExtractDslMetaDataTask.groovy
parse(f, repository) counter++ } //updating/modifying the metadata and making sure every type reference across the metadata is fully qualified //so, the superClassName, interfaces and types needed by declared properties and declared methods will have fully qualified name
Groovy - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Mon Jan 08 12:45:57 GMT 2024 - 4.4K bytes - Viewed (0) -
.github/workflows/CheckBadMerge.groovy
} } /** * Check if the given file is "bad": we should only use the release note from the master branch. * This means that every line in the merge commit version should be either: * - Only exists on `master`. * - Exists on `master` and `releaseX`. * If any line is only present on `releaseX` version, then it's a bad file.
Groovy - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Dec 19 10:35:44 GMT 2023 - 6.5K bytes - Viewed (0) -
.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 May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 3K 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 # within the file. We keep each automation (or very closely related group of automations) in
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2K bytes - Viewed (0)