merge-dependency-updates

Triages open bot pull requests and produces a merge-readiness dashboard with CI and review status.

1.2k|337|Updated Oct 13, 2022
One-click install
npx skills add https://github.com/dotnet/dotnet --skill merge-dependency-updates
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-dependency-updates
Source: https://github.com/dotnet/dotnet/tree/main/src/msbuild/.github/skills/merge-dependency-updates
Command: npx skills add https://github.com/dotnet/dotnet --skill merge-dependency-updates

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually checking every open bot pull request (dependency updates, codeflow, OneLoc localization) across branches is slow and error-prone. This Skill gathers all open bot PRs in one pass, flags suspicious file changes, and produces a single clickable dashboard so maintainers can approve or reject each PR quickly.

Core Features & Use Cases

  • Bot PR Discovery: Searches GitHub for open PRs from dotnet-maestro (dependency updates and codeflow) and dotnet-bot (OneLoc localization) in parallel.
  • Status Dashboard: Queries CI status, review decisions, approvals, unresolved review threads, and changed files via the GitHub GraphQL API, then renders grouped tables with status icons and links.
  • Merge Readiness Automation: Updates PR branches with the updatePullRequestBranch mutation and bumps VersionPrefix in eng/Versions.props for servicing branches older than vs18.10.
  • Suspicious File Detection: Flags PRs whose changed files fall outside expected patterns (e.g., src/ changes in a codeflow PR, non-localization files in a OneLoc PR).
  • Use Case: A maintainer opens the repo on Monday, runs the triage, and gets a dashboard showing 3 dependency PRs ready to merge, 1 codeflow PR needing review, and 1 OneLoc PR blocked for reverting translations.

Quick Start

Triage all open bot pull requests in the dotnet/msbuild repository and show me a dashboard of their CI and review status.

Frequently Asked Questions about merge-dependency-updates

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

FAQPage Schema
How do I review all open dependency update PRs at once?

Search GitHub for open PRs authored by app/dotnet-maestro, then query each PR's CI status, review decision, and changed files via the GraphQL API. The results are grouped into a dashboard table so you can approve or reject each PR in one pass.

How do I update a pull request branch with the GitHub API?

Use the GraphQL updatePullRequestBranch mutation with the PR's node ID, which is the API equivalent of clicking the Update branch button. If it fails due to conflicts GitHub cannot auto-resolve, fall back to a local git merge.

What files should a dotnet-maestro dependency update PR change?

Arcade dependency updates should only touch files under eng/ and global.json, while roslyn, nuget, or runtime updates should only modify eng/Version.Details.xml and eng/Version.Details.props. Any file outside these patterns is flagged as suspicious.

When should I bump VersionPrefix for a dependency update PR?

Bump the patch component of VersionPrefix in eng/Versions.props only for vs* servicing branches older than vs18.10. Branches vs18.10 and newer, as well as main, do not require a version bump for dependency updates.

Why would a OneLoc localization PR be blocked from merging?

A OneLoc PR is blocked when reviewers flag it for reverting existing translations or when it modifies files outside the expected xlf and resx localization paths. In that case, do not merge and wait for updated translations.