actions-debugging

Debug failing GitHub Actions CI by listing workflows, filtering run details by status or branch, and fetching job logs. You identify root causes through structured access to Actions data, enabling automated analysis and fix recommendations.

Retrieve GitHub Actions failed job logs with optional tailing to focus on error sections. This isolates CI pipeline failures by pulling specific log segments to identify root causes without leaving the terminal.

Investigate flaky tests by filtering recent GitHub Actions workflow runs by status or branch. Examining run timing and resource usage across multiple runs helps identify performance bottlenecks and diagnose inconsistent CI failures.

This GitHub Actions debugging approach works without extra dependencies. It utilizes Copilot CLI's built-in GitHub MCP server methods for structured access to Actions data, requiring no external components or packages.

Audit GitHub Actions deployment durations by examining run timing and resource usage metrics. This usage analysis identifies performance bottlenecks and evaluates deployment durations directly from your repository workflow data.