Global error detection settings now allow multiple error regex patterns. Multiple patterns are supported using multi-line YAML format, allowing you to detect errors from different tools with various output formats. Added error detection settings to the repository CR. By default, error detection uses the global pattern. However, you can customize error detection patterns on a per-repository basis using the Repository CR. You can specify multiple regex patterns to detect different error formats in your repository. Each pattern must use [named groups]( https://www.regular-expressions.info/named.html ) to capture: - `filename`: The file path where the error occurred - `line`: The line number - `error`: The error message - `column`: (optional) The column number **Configuration Options:** - `enabled`: **Required** boolean flag to enable or disable error detection for this   repository. Set to `true` to enable or `false` to disable error detection.   This field must be explicitly specified when configuring error detection settings. - `patterns`: Array of regex patterns. Repository-specific patterns are tried   first, followed by global patterns. If not specified or empty, only the   global patterns are used. **Note:** Providing an empty array does not disable   error detection; it falls back to using only the global patterns defined in   the `pipelines-as-code` ConfigMap. - `max_number_of_lines`: Number of log lines to scan (overrides global   setting). Default is 50. Use -1 for unlimited. You can explicitly disable error detection for a specific repository, even if it's enabled globally. If you don't need to customize error detection for repository, simply omit the entire `error_detection` field and the global settings will be used.