pr-action-analyzer

To analyze GitHub PR CI failures, you provide a PR URL and specify an action type like UT, SLIT, or E2E. The tool fetches check runs via gh CLI, parses the logs, and outputs a structured report highlighting failing tests and error patterns.

Yes, PR CI failure analysis works with Argo workflow data for E2E failures. It can parse Argo workflow logs to locate relevant E2E checks, extract failing tests, and surface the underlying error patterns causing the CI pipeline to fail.

Yes, you can extract failing tests from GitHub check runs automatically. By fetching the CI logs through the gh CLI, the analysis categorizes checks into UT, SLIT, or E2E and parses them to isolate specific failing tests and error messages.

The best way to categorize PR checks for targeted log analysis is by dividing them into UT, SLIT, and E2E groups. This categorization helps target the specific CI logs needed to extract error messages and generate actionable failure reports.

You need the gh CLI for diagnosing PR CI failures because it is the mechanism used to fetch GitHub check runs and their associated logs. The analysis relies on this data to locate failing tests and identify the root causes of the failures.

From E2E failure log analysis, you can expect structured failure reports containing actionable insights for developers. These reports surface failing tests, extract error patterns from the parsed logs, and identify the root causes of the CI failures.