gh-debug

Debug GitHub Actions workflow failures by fetching and analyzing run logs to identify root causes. The diagnostic process streams logs, filters errors, and generates a report with targeted error context and actionable next steps.

Diagnose flaky CI/CD pipelines by fetching and parsing workflow logs for the failed run. The analyzer filters errors, caps results, and produces a clear diagnostic report with actionable next steps to resolve intermittent pipeline failures.

Analyze GitHub Actions logs by invoking a Python-based log analyzer script with a run-id or workflow URL. The script streams workflow logs, filters errors, and can cap results to provide targeted error diagnostics for failed runs.

Manual inspection of GitHub Actions logs is supported as a fallback workflow. If the primary automated Python log analyzer fails to diagnose the workflow failure, you can manually inspect the fetched logs to identify the root cause.

GitHub Actions workflow failures are identified by fetching and analyzing workflow logs to parse errors. The log analyzer streams the logs, filters errors, and generates a diagnostic report with targeted error context and actionable next steps.

Yes, this log analysis approach applies to failed runs and flaky pipelines across GitHub Actions workflows. It fetches the specific workflow logs for the run-id provided and applies error diagnostics to identify the root cause.