Skip to content

understanding-openshift-prs

Use when managing or shepherding open OpenShift pull requests — explains what a PR needs to merge (lgtm, approved, verified, Jira labels), pre-merge verification with /verified, why e2e jobs have not started (pipeline controller, /lgtm, /pipeline required), Chai bot test selection, Jira label failures, backports with /cherry-pick, and how to prove a fix worked from presubmit artifacts and draft a /verified comment for human approval.

Plugin: ci

Usage

/ci:understanding-openshift-prs

Source

View plugins/ci/skills/understanding-openshift-prs/SKILL.md on GitHub