Uh oh!
There was an error while loading. Please reload this page.
[skill] Use Version.Details.xml as VMR snapshot fallback for manual backflow - #124129
Conversation
There was a problem hiding this comment.
Pull request overview
Improves reliability of GitHub “skills” automation scripts by (1) making VMR snapshot detection resilient to manual backflow commit message formats and (2) working around a Helix API artifact URI bug for subdirectory files.
Changes:
- Add a fallback to read
eng/Version.Details.xmlon the PR branch to infer the VMR snapshot SHA when commit messages aren’t parseable. - Improve snapshot validation messaging (identify whether snapshot came from commit messages vs
Version.Details.xml). - Rebuild Helix artifact file URIs from
FileNamefor subdirectory artifacts and document the known Helix API issue.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
.github/skills/vmr-codeflow-status/scripts/Get-CodeflowStatus.ps1 | Adds Version.Details.xml fallback and refines snapshot validation/status output. |
.github/skills/azdo-helix-failures/scripts/Get-HelixFailures.ps1 | Workaround for broken Helix artifact URIs for files in subdirectories by reconstructing URLs. |
.github/skills/azdo-helix-failures/references/helix-artifacts.md | Documents the Helix API bug and the script’s workaround. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
b9b70b4 to
3090c43Compare3090c43 to
3969355Compare3969355 to
b5e3166Compare2fa670d to
33ae35fCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
33ae35f to
0062b79Compare0062b79 to
c0c18fdCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Version.Details.xml's <Source Sha=...> is the authoritative record of which VMR commit a product repo branch is based on. Previously the script treated it as a fallback after commit message parsing. Now it's checked first, with commit messages as secondary confirmation. This correctly handles: - Manual backflow (darc vmr backflow pushed directly) - Normal codeflow (Maestro-managed) - Conflicted PRs (VD.xml reflects pre-codeflow state) - Forward flow PRs (skips VD.xml, uses commit messages) Tested against sdk#52727 (manual backflow) and sdk#52885 (conflicted).
-CheckMissing now scans open forward flow PRs (product repo → dotnet/dotnet) in addition to missing backflow PRs. For each forward flow PR it detects: - Conflict (Maestro 'Conflict detected' comment) - Staleness (opposite codeflow merged while PR was open) - Healthy (no issues) Summary section now shows both directions. Also fixes: dotnet-maestro comment author matching (gh CLI returns 'dotnet-maestro' not 'dotnet-maestro[bot]' for login field). Tested against dotnet/sdk (4 forward PRs: 2 healthy, 1 stale, 1 conflict) and dotnet/runtime (3 forward PRs: 2 healthy, 1 stale).
5cc04ae to
adc8cb1Compare6daddd0 to
9d21ee3CompareThere was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
Comments suppressed due to low confidence (1)
.github/skills/vmr-codeflow-status/scripts/Get-CodeflowStatus.ps1:265
- Forward-flow lookup derives
$repoShortNameby stripping only thedotnet/prefix. If-Repositoryis ever used with a non-dotnet/*repo, this produces an invalid search string (e.g.,dotnet/otherOwner/repo). Consider deriving the repo name via($Repository -split '/',2)[1](or parsing owner/name once) so the search is robust and independent of the owner.
Write-Host " ✅ Open backflow PR #$($openBranches[$branchName]) exists" -ForegroundColor Green
$coveredCount++
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
- Use 2>$null instead of 2>&1 for gh pr view to prevent stderr corrupting JSON stream - Wrap ConvertFrom-Json in try/catch for forward flow PR details - Tighten regex fallback to require exactly 40-char hex SHA - Use case-insensitive StringComparison for SHA matching
9d21ee3 to
7ed5756CompareUh oh!
There was an error while loading. Please reload this page.
…ackflow (dotnet#124129) ## Version.Details.xml as primary VMR snapshot source + forward flow scanning ### Problem The codeflow status script relied on PR body metadata and commit messages to determine the VMR snapshot. When manual backflow was used (e.g., \darc vmr backflow\ pushed directly), the PR body was stale and commit messages didn't follow the expected format, causing incorrect freshness reporting. ### Changes **Commit 1: VD.xml as primary snapshot** - \�ng/Version.Details.xml\ (\<Source Sha=...>\) is now checked first as the authoritative snapshot source - XML parser with regex fallback, 40-char SHA validation - Commit messages are secondary confirmation, PR body is last resort - Case-insensitive SHA comparison throughout - \2>\\\ for stderr isolation on all \gh\ calls **Commit 2: Forward flow scanning in -CheckMissing** - \-CheckMissing\ now scans open forward flow PRs (product repo → dotnet/dotnet) - Detects conflicts and staleness via Maestro comment scanning - Combined summary showing backflow + forward flow health ### Testing - VD.xml: Tested against sdk#52727 (manual backflow mismatch), sdk#52885 (conflicted), aspnetcore#65338 (deleted branch), runtime#124098 (normal), sourcelink#1581 (fresh) - Forward flow: Tested against dotnet/sdk (4 PRs: 2 healthy, 1 stale, 1 conflict) and dotnet/runtime (3 PRs: 2 healthy, 1 stale) Cross-repo context: dotnet/sdk#52727, dotnet/sdk#52885
Version.Details.xml as primary VMR snapshot source + forward flow scanning
Problem
The codeflow status script relied on PR body metadata and commit messages to determine the VMR snapshot. When manual backflow was used (e.g., \darc vmr backflow\ pushed directly), the PR body was stale and commit messages didn't follow the expected format, causing incorrect freshness reporting.
Changes
Commit 1: VD.xml as primary snapshot
Commit 2: Forward flow scanning in -CheckMissing
Testing
Cross-repo context: dotnet/sdk#52727, dotnet/sdk#52885