Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 14 for Command (0.17 sec)

  1. .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.7K bytes
    - Viewed (0)
  2. .github/ISSUE_TEMPLATE/30_contributor_regression.yml

        validations:
          required: true
      - type: input
        id: build-scan-url
        attributes:
          label: Build scan URL (optional)
          description: |
            You can run your build command with `--scan` to publish a Build Scan to [scans.gradle.com](https://scans.gradle.com/).
        validations:
          required: false
      - type: textarea
        id: environment
        attributes:
    Others
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Feb 16 07:49:32 GMT 2024
    - 2.7K bytes
    - Viewed (0)
  3. .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 2K bytes
    - Viewed (0)
  4. .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Mon Apr 22 15:32:31 GMT 2024
    - 2.5K bytes
    - Viewed (0)
  5. .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 3K bytes
    - Viewed (0)
  6. .github/workflows/CheckBadMerge.groovy

            return new ExecResult(stderr: stderr, stdout: stdout, returnCode: returnCode)
        }
    
        static String getStdout(String command) {
            ExecResult execResult = exec(command)
    
            assert execResult.returnCode == 0: "$command failed with return code: $execResult"
            return execResult.stdout
        }
    
        static Future<String> readStreamAsync(InputStream inputStream) {
    Groovy
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Tue Dec 19 10:35:44 GMT 2023
    - 6.5K bytes
    - Viewed (0)
  7. .teamcity/src/main/kotlin/util/AdHocPerformanceScenario.kt

    fun ParametrizedWithType.profilerParam(defaultProfiler: String) {
        text(
            "profiler",
            defaultProfiler,
            display = ParameterDisplay.PROMPT,
            allowEmpty = false,
            description = "Command line option for the performance test task to enable profiling. For example `async-profiler`, `async-profiler-heap`, `async-profiler-all` or `jfr`. Use `none` for benchmarking only."
        )
    }
    
    Plain Text
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Tue Feb 13 13:53:39 GMT 2024
    - 4.9K bytes
    - Viewed (2)
  8. .github/workflows/codeql-analysis.yml

        - name: Cleanup Gradle Daemons
          run: ./gradlew --stop
          if: ${{ matrix.language == 'java' }}
    
        # ℹī¸ Command-line programs to run using the OS shell.
        # 📚 https://git.io/JvXDl
    
        # ✏ī¸ If the Autobuild fails above, remove it and uncomment the following three lines
    Others
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Tue Jan 30 18:26:59 GMT 2024
    - 4K bytes
    - Viewed (0)
  9. .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 Apr 24 11:36:11 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 2.4K bytes
    - Viewed (0)
  10. .teamcity/mvnw.cmd

    @REM ----------------------------------------------------------------------------
    
    @REM Begin all REM lines with '@' in case MAVEN_BATCH_ECHO is 'on'
    @echo off
    @REM set title of command window
    title %0
    @REM enable echoing by setting MAVEN_BATCH_ECHO to 'on'
    @if "%MAVEN_BATCH_ECHO%" == "on"  echo %MAVEN_BATCH_ECHO%
    
    @REM set %HOME% to equivalent of $HOME
    Batch File
    - Registered: Wed Apr 24 11:36:11 GMT 2024
    - Last Modified: Wed Feb 26 01:48:39 GMT 2020
    - 6.5K bytes
    - Viewed (0)
Back to top