You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-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).
- You need to check if a specific fix has flowed through the VMR pipeline to a codeflow PR
15
17
- A PR has a Maestro staleness warning ("codeflow cannot continue") or conflict
16
18
- You need to understand what manual commits would be lost if a codeflow PR is closed
17
-
- You want to know if expected backflow PRs are missing for a repo/branch
18
-
- Asked questions like "is this codeflow PR up to date", "has the runtime revert reached this PR", "why is the codeflow blocked"
19
+
- You want to check the overall state of flow for a repo (backflow and forward flow health)
20
+
- Asked questions like "is this codeflow PR up to date", "has the runtime revert reached this PR", "why is the codeflow blocked", "what is the state of flow for the sdk"
0 commit comments