- Sort Score
- Result 10 results
- Languages All
Results 1 - 9 of 9 for Command (0.16 sec)
-
.cm/complex_changes.cm
approvals: 2 # To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # This section could also appear ahead of the automations section.
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/lacks_tests.cm
# To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # This section could also appear ahead of the automations section. colors: yellow: 'ffb300' includes_src_changes: {{ files | match(regex=r/.*\/src\//) | some }}
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) -
architecture/README.md
## Gradle runtimes Gradle is also made up of several different processes that work together to "run the build", such as the Gradle daemon and the `gradlew` command. Each process, or "runtime", applies different constraints to the code that runs in that process. For example, each process has different supported JVMs and a different set of services available for dependency injection.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 2.4K bytes - Viewed (0) -
.cm/estimated_time_to_review.cm
# To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # This section could also appear ahead of the automations section. # This function calculates the estimated time to review and makes it available in the automation above.
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) -
.cm/platform_labels.cm
{% endfor %} # To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # TODO: It would be very nice to avoid having this list somehow, but it needs to be defined in YAML and not in JS for the looping template to work
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Mon Apr 22 15:32:31 GMT 2024 - 2.5K bytes - Viewed (0) -
.cm/misc_labels.cm
color: 'E94637' # To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # The results of these calculations are assigned to `is.formatting`, `is.docs` and `is.tests`. is: formatting: {{ source.diff.files | isFormattingChange }}
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/includes_todos.cm
# To simplify the automations section, some calculations are placed under unique YAML keys defined here. # Read the "|" not as "or", but as a "pipe", taking the output of the previous command and passing it to the next command. # This section could also appear ahead of the automations section. colors:
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Fri Apr 12 13:42:16 GMT 2024 - 1.9K bytes - Viewed (0) -
architecture/runtimes.md
- Gradle daemon. This is the process that actually runs the build. It hosts build logic and coordinates the lifecycle of the build. It is a long-running daemon process. - CLI client. This is the `gradle` or `gradlew` command, and is responsible for locating, starting and interacting with the Gradle daemon, potentially downloading the Gradle distribution.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 06:42:46 GMT 2024 - 2.3K bytes - Viewed (0) -
CONTRIBUTING.md
This may help you better understand and contribute to Gradle. ### Debugging Gradle You can debug Gradle by adding `-Dorg.gradle.debug=true` to the command-line. Gradle will wait for you to attach a debugger at `localhost:5005` by default. If you made changes to build logic in the `build-logic` included build, you can run its tests by executing `./gradlew :build-logic:check`.
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Sat May 04 07:43:02 GMT 2024 - 15.6K bytes - Viewed (0)