psOutput.forEach(line -> {
            Matcher commandLineArgsMatcher = commandLineArgsPattern.matcher(line);
            Matcher pidMatcher = pidPattern.matcher(line);
            if (commandLineArgsMatcher.find() && pidMatcher.find()) {
                String pid = pidMatcher.group(1);
                if (!MY_PID.equals(pid)) {
                    action.accept(pid, line);
                }
            }

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`.

}

const isString = subject => typeof subject === 'string'

// > A blank line matches no files, so it can serve as a separator for readability.
const checkPattern = pattern => pattern
    && isString(pattern)
    && !REGEX_TEST_BLANK_LINE.test(pattern)
    && !REGEX_INVALID_TRAILING_BACKSLASH.test(pattern)

    // > A line starting with # serves as a comment.
    && pattern.indexOf('#') !== 0

    <suppress checks="InterfaceIsTypeCheck"
              files=".*[/\\]core-api[/\\]src[/\\]main[/\\]java[/\\]org[/\\]gradle[/\\]api[/\\]attributes[/\\]Usage.+"/>

    <!-- We like it explicit -->
    <suppress checks="ExplicitInitializationCheck"
              files=".*"/>

    <!-- Ignore code from maven subproject under org.apache -->
    <suppress checks="RegexpSingleline"