Pull Request Overview

This PR fixes an issue with the regex used to match API error messages by removing the regex boundaries so that error messages containing extra context can be detected for proper telemetry reporting. It also adds additional tests to verify the behavior of getActionsStatus and wrapApiConfigurationError functions across both TypeScript and JavaScript implementations.

• Updated the regex pattern in API client files to remove boundaries.
• Added test cases for getActionsStatus and API error wrapping behavior.
• Extended imports and helper functions in test files to support the new error handling logic.

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.

src/status-report.test.ts:214

• The test description for a ConfigurationError with an additional failure cause states it should return 'failure', but the expected result is 'user-error'. Please update the description to accurately reflect the expected outcome.

t.is(getActionsStatus(new ConfigurationError("exit code 1"), "multiple things went wrong"), "user-error", "getActionsStatus should return failure if passed a configuration error and an additional failure cause");

src/api-client.ts:248

• Removing the regex boundaries could allow unintended partial matches; please confirm that this broader matching is intended and consider adding comments or tests to ensure it doesn't capture unwanted error messages.

/ref .* not found in this repository/.test(e.message)

lib/api-client.js:209

• Similar to the TypeScript version, removing the regex boundaries here may lead to broader than intended matches. Confirm this change with appropriate documentation or tests to avoid potential false positives.

/ref .* not found in this repository/.test(e.message)

Tip: Copilot only keeps its highest confidence comments to reduce noise and keep you focused. Learn more

Thanks for adding tests!