fix-ci-failure

To fix a failing GitHub Actions CI workflow, identify the failing job and step from the logs, categorize the failure type, and apply minimal corrective edits to the workflow configuration or repository source. Local verification with equivalent commands ensures the fix prevents unrelated refactors.

CI pipeline failures suitable for root cause analysis include lint/format errors, type-check failures, test failures, build compilation issues, structural path problems, permission/token problems, and timeouts that block pull requests.

Yes, you can resolve GitHub Actions timeouts and permission/token errors by reading the relevant workflow configuration files with enough surrounding context to locate the true root cause, then applying the smallest necessary change to unblock the pipeline.

The best way to ensure a CI fix avoids unrelated refactors is to apply minimal, safe corrective edits and then run the workflow's appropriate local equivalent command to verify the specific fix and check for secondary failures.

To find the root cause of a build compilation failure in a CI pipeline, locate the failing job and step, then read the relevant source files with enough surrounding lines around the error location to identify the true structural or code-level issue.

No, fixing a GitHub Actions test failure does not require reading the entire source. Context-first debugging locates the failing step and reads only the relevant workflow and source files with enough surrounding lines to identify the root cause.