- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 87 for mention (0.24 sec)
-
docs/metrics/prometheus/README.md
The command will generate the `scrape_configs` section of the prometheus.yml as follows: ##### Cluster ```yaml scrape_configs: - job_name: minio-job bearer_token: <secret> metrics_path: /minio/v2/metrics/cluster
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Fri Apr 12 15:49:30 GMT 2024 - 7.1K bytes - Viewed (0) -
docs/tr/docs/external-links.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Tue Jan 09 15:28:47 GMT 2024 - 1.1K bytes - Viewed (0) -
ReadMe.md
It's expected that `verification-metadata.xml` should only be updated with the commits that modify the build. There are some tips how to perform such updates: - Delete `components` section of `verification-metadata.xml` to avoid stockpiling of old unused dependencies. You may use the following command: ```bash #macOS sed -i '' -e '/<components>/,/<\/components>/d' gradle/verification-metadata.xml
Plain Text - Registered: Fri May 03 08:18:13 GMT 2024 - Last Modified: Thu Apr 11 14:28:46 GMT 2024 - 8.7K bytes - Viewed (0) -
docs/de/docs/external-links.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Wed Feb 21 22:23:00 GMT 2024 - 1.4K bytes - Viewed (0) -
docs/es/docs/external-links.md
Plain Text - Registered: Sun May 05 07:19:11 GMT 2024 - Last Modified: Fri Feb 02 18:09:12 GMT 2024 - 1.1K 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'
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/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) -
.cm/complex_changes.cm
args: 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) -
Development.md
The suggestions are displayed in the separate "Try"- section of the console output. The suggestions are collected in the `BuildExceptionReporter` and printed to the console. In some cases, you still want to keep the old behavior and display the suggestions in the error message. ### Add custom suggestions
Plain Text - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Tue Feb 06 22:54:40 GMT 2024 - 1.8K bytes - Viewed (0) -
.cm/estimated_time_to_review.cm
run: - action: add-label@v1 # etr is defined in the last section of this example args: label: "{{ calc.etr }} min review" color: {{ 'E94637' if (calc.etr >= 20) else ('FBBD10' if (calc.etr >= 5) else '36A853') }} # To simplify the automations section, some calculations are placed under unique YAML keys defined here.
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)