skills.rest
dotnet
dotnetOFFICIAL
Explore all skills by this author →
Website𝕏@dotnetfdnGitHub

pr-build-status

Retrieve Azure DevOps build IDs and Helix test logs for GitHub PRs.

23.3k|2.0k|Updated May 8, 2020
Search Tags:#GitHub#Azure DevOps#PowerShell#CI#Helix#pr-build-status
One-click install
npx skills add https://github.com/dotnet/maui --skill pr-build-status
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-build-status
Source: https://github.com/dotnet/maui/tree/main/.github/skills/pr-build-status
Command: npx skills add https://github.com/dotnet/maui --skill pr-build-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Retrieve Azure DevOps build information for GitHub Pull Requests, including build IDs, stage status, failed jobs, and Helix console logs for any Helix-based test failures.

Core Features & Use Cases

  • Fetch PR build IDs across pipelines and visualize status
  • Inspect failed jobs and summarize issues for quick triage
  • Retrieve Helix test logs to diagnose device/integration test failures
  • Use during PR reviews to provide actionable CI feedback and remediation steps

Quick Start

pwsh .github/skills/pr-build-status/scripts/Get-PrBuildIds.ps1 -PrNumber 123

Frequently Asked Questions about pr-build-status

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

FAQPage Schema
How do I get Azure DevOps build IDs for a GitHub pull request?▼

You can retrieve Azure DevOps build IDs for a GitHub PR by running the Get-PrBuildIds PowerShell script with the specific PR number. This fetches build information across pipelines and visualizes the current status for quick triage.

How do I retrieve Helix test logs for failed device integration tests in Azure DevOps?▼

Retrieve Helix test logs for failed device integration tests by running the provided PowerShell script during your PR review. It automatically fetches Helix console logs to help diagnose test failures across the dotnet/maui repository pipelines.

Do I need PowerShell and GitHub CLI to check PR build status in Azure DevOps?▼

Yes, you need PowerShell (pwsh) and GitHub CLI (gh) authentication to access the target dotnet/maui repository. These prerequisites are required to authenticate and retrieve PR build IDs and Helix test logs from Azure DevOps.

What is the best way to triage failed CI jobs in Azure DevOps pipelines for GitHub PRs?▼

The best way to triage failed CI jobs is to use a script that inspects failed jobs and summarizes issues. It retrieves PR build IDs across pipelines, visualizes stage status, and provides actionable CI feedback for remediation.

Can I view stage status and failed jobs across multiple pipelines for a single GitHub PR?▼

Yes, you can view stage status and failed jobs across multiple pipelines for a single GitHub PR. The skill fetches build IDs across all associated pipelines and summarizes the stage status and failed jobs for quick triage.

Related Skills

Explore More Software Engineering Skills→
DataDogDataDog
570

analyze-azdo-build

Analyze Azure DevOps CI build failures and categorize issues by pull request or build ID.

Official
Advanced
dotnetdotnet
13

helix-investigation

Diagnose Helix test failures by collecting AzDO timelines, job data, and console logs.

Official
Advanced
PracticalSwanPracticalSwan
7

devops-tooling

Guide Git workflows, Bash and PowerShell scripting, and CI/CD pipelines.

Community
Intermediate
malwarebomalwarebo
5

azure-pipelines

Manage Azure DevOps pipeline builds via the Azure CLI.

Community
Intermediate