ci-error-fix

Diagnose CI pipeline failures by reviewing error logs, categorizing the issue type (build, lint, test, or configuration), then reproducing it locally to validate fixes before pushing. This structured workflow reduces debugging time and prevents regressions.

Pull your feature branch, replicate the CI environment locally, run the failing build or tests, and confirm the error matches what the pipeline reported. Once you fix it locally, re-run the tests and linting to verify the fix before committing.

Check your main branch against the same CI pipeline to establish parity. If main passes, the failure is new to your changes; if main fails identically, the issue pre-exists and may require a different resolution strategy.

Follow a guided workflow: understand the error type, verify main-branch parity, reproduce locally, apply a minimal fix targeting only the reported issue, then re-run CI verification. This prevents introducing new failures while fixing the original one.

Yes, run the full test suite and linting checks locally after applying your fix to ensure you haven't introduced regressions. Verify the entire CI pipeline passes before merging.