GitHub Actions: understand the failed job before changing the pipeline

Three different problems can make the same job red

A failing command can mean the runner uses a different dependency or working directory. A failing assertion can mean the application has a real defect. An authentication failure can mean an account holder needs to renew access. These are different outcomes; a green badge alone does not distinguish them.

• Configuration repair: preserve the checks and make the named job execute successfully.
• Application repair: capture a failing regression test, then repair the behaviour it exposes.
• Access or provider issue: retain the redacted error and route it to the account holder; do not replace secrets in an enquiry.

Record the execution context

Keep the workflow file name, job name, run identifier, attempt, event, tested revision and runner label together. A pull request commonly runs against a synthetic merge commit, not just the branch head. A rerun archive may contain only rerun jobs, so an earlier attempt can be needed for the baseline.

• For a matrix, identify the failing operating system and runtime combination.
• Record the first relevant error, not only the final exit code.
• Before any rerun, ask whether another job on the same event deploys or has external effects.

Choose one-off repair or an ongoing responsibility

One repeatable job with a safe branch run is a bounded repair. Several unrelated failures, intermittent tests or inaccessible runners need a broader investigation. Keeping CI green is a standing responsibility with agreed repositories, triggers, exclusions and escalation; it is not a promise that every third-party service stays available.

• A skipped job, ignored failure or weakened assertion is not a repair.
• Merge, repository settings and production deployments stay under the customer's approval rules.

Ask for the right work

Start with the named job, redacted error, event and whether running it can deploy. Do not send repository code, credentials or invitations in the first enquiry. We confirm scope and the authorised test route before access. Existing catalogue prices are untested hypotheses; broader or recurring work needs a written quote.