- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 37 for Hevery (0.15 sec)
-
.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 # within the file. We keep each automation (or very closely related group of automations) in
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) -
.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 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 2K 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 01 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 3K 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 # within the file. We keep each automation (or very closely related group of automations) in
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) -
.github/workflows/feedback.yml
name: Feedback on: schedule: - cron: '0 * * * *' # every hour workflow_dispatch: jobs: feedback: runs-on: ubuntu-latest permissions: issues: write pull-requests: write steps: # Feedback loop: ask for something on PR/Issue and close if not provided or return to the queue on update. # https://github.com/gradle/issue-management-action/blob/main/src/feedback.ts
Others - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon Jan 22 06:29:03 GMT 2024 - 499 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 # within the file. We keep each automation (or very closely related group of automations) in
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) -
.teamcity/src/main/kotlin/model/CIBuildModel.kt
// Include cross version tests, these take care of selecting a very small set of versions to cover when run as part of this stage, including the current version quick(true, true, true, 120, 4), // Include cross version tests, these take care of selecting a very small set of versions to cover when run as part of this stage, including the current version platform(true, true, true),
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Fri Feb 23 01:54:48 GMT 2024 - 20.9K bytes - Viewed (0) -
.teamcity/src/test/kotlin/ApplyDefaultConfigurationTest.kt
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Wed Apr 24 08:17:56 GMT 2024 - 6.5K 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 01 11:36:15 GMT 2024 - Last Modified: Tue Dec 19 10:35:44 GMT 2023 - 6.5K bytes - Viewed (0)