skills.rest
openshift-eng
openshift-engOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Fetch New PRs in Payload

Identify pull requests added in an OpenShift payload versus the previous payload.

1|Updated Apr 29, 2026
Search Tags:#automation#diff#pr#openshift#sippy#payload#release-controller
One-click install
npx skills add https://github.com/openshift-eng/ga-regression-reports --skill fetch-new-prs-in-payload
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Fetch New PRs in Payload
Source: https://github.com/openshift-eng/ga-regression-reports/tree/main/.claude/skills/fetch-new-prs-in-payload
Command: npx skills add https://github.com/openshift-eng/ga-regression-reports --skill fetch-new-prs-in-payload

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies which pull requests were added in a given OpenShift payload compared to the previous payload, enabling teams to correlate changes with releases and potential regressions.

Core Features & Use Cases

  • Surface new PRs introduced in a payload and their linked bug reports for quick triage.
  • Output formats include JSON for automation and a readable summary for quick reviews.
  • Use case: after a release candidate, compare payloads to understand what shipped and which PRs might relate to observed issues.

Quick Start

Run the script with a payload tag to fetch and display new PRs.

Frequently Asked Questions about Fetch New PRs in Payload

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify which pull requests were added in a specific OpenShift payload?▼

To identify new pull requests in an OpenShift payload, you fetch a payload diff comparing the target release to the previous one. This surfaces the exact PRs introduced and their linked bug reports for quick triage.

What is the best way to compare OpenShift payloads to find new PRs after a release candidate?▼

Comparing OpenShift payloads to find new PRs is best handled by querying the Sippy payload diff API. If Sippy does not cover the payload, the process falls back to the release controller API for recent or in-progress releases.

Can I get the OpenShift payload diff output as JSON for automation?▼

Yes, you can get OpenShift payload diff output as JSON for automation. The output structure includes payload_tag, total_prs, and pull_requests fields, alongside a human-readable summary format for quick reviews.

Does the Sippy payload diff API support in-progress OpenShift releases?▼

The Sippy payload diff API may not fully support in-progress OpenShift releases. When Sippy lacks the data, the process falls back to the release controller API to identify new PRs for recent or in-progress payloads.

Why do I need to track new PRs introduced between OpenShift payload releases?▼

Tracking new PRs introduced between OpenShift payload releases is needed to correlate code changes with releases and potential regressions. It enables teams to quickly understand what shipped and which PRs relate to observed issues after a release candidate.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng

Fetch Payloads

Fetch OpenShift release payloads and output structured JSON with tag details.

Official
Intermediate
semicolon-devteamsemicolon-devteam

collect-bug-reports

Aggregate open bug reports from repositories into consolidated JSON or Markdown reports.

Official
Intermediate
openshift-engopenshift-eng
112

Get Release Dates

Fetch OpenShift release dates and metadata from the Sippy API.

Community
Basic
openshift-engopenshift-eng

Fetch Releases

Query the Sippy API to retrieve latest or all OCP releases.

Official
Intermediate