Develop CI Pipelines

Trace the affected event through workflow creation, job selection, dependencies, commands, artifacts, and deployment. Diagnose the first failing transition from its configuration and run evidence.

Read provider behavior, then the affected provider: GitHub Actions, GitLab CI, or [Bitbucket Pipelines][ref-1].

Reuse existing [local feedback][local-feedback] when it is already configured. Follow [bounded CI evidence][ci-evidence] before fetching failure logs. Do not install Git hooks unless repository policy or a hook-specific task requires it.

Use provider-native YAML. Keep required failures visible. Pin executable dependencies and identify artifact producer revisions. Trace control of checkout content, interpolated inputs, caches, artifacts, runners, and credentials before privileged execution.