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
Copy file name to clipboardExpand all lines: .claude/commands/branch-status.md
+82-6Lines changed: 82 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,9 +42,24 @@ Parse the JSON and produce a report with two sections.
42
42
43
43
### GitHub PRs
44
44
45
-
For each repo with a PR, show: repo name, PR title, approval state (N approved / M changes requested / K pending reviewers), CI rollup, draft status, and mergeability. Group repos with no PR separately.
45
+
For each repo with a PR, show: repo name, PR title, approval state (N approved / M changes requested / K pending reviewers), CI rollup, draft status, and a "Ready" column. Group repos with no PR separately.
46
46
47
-
Call out blockers explicitly: PRs needing approvals, PRs with changes requested, CI failures, draft PRs that need to be un-drafted, and merge conflicts.
47
+
The "Ready" column reflects whether this PR is ready to merge, combining GitHub mergeability and task list completion:
48
+
- "Yes" — GitHub says MERGEABLE and no unchecked blocker tasks (or no task list)
49
+
- "Tasks pending" — GitHub says MERGEABLE but has unchecked blocker tasks
For the CI column, use title case: Success, Failure, Pending — not all caps.
54
+
55
+
Call out blockers explicitly: PRs needing approvals, PRs with changes requested, CI failures, draft PRs that need to be un-drafted, merge conflicts, and unchecked blocker tasks.
56
+
57
+
For each PR that has task list items (from `task_items` in the JSON) or linked issues with task items (from `linked_issues[].task_items`), list unchecked items grouped by whether they are blockers or deferrable. Show PR task items and linked issue task items together, labelling the source when both are present (e.g. "PR task list" vs "Issue #123 task list").
58
+
59
+
-**Deferrable** (OK to be incomplete at merge time): "TeamCity verify and merge" or similar CI-trigger tasks; "user education handoff", "customer comms", "documentation handoff", or any post-merge communication/education step.
60
+
-**Blockers** (must be complete before merge): "manual test", "manual testing", "automated test", "write test/tests", "QA", or any other pre-merge validation step. When in doubt, treat an unchecked item as a blocker.
61
+
62
+
Note: LabKey PRs are often approved during code review, which may happen before testing is complete. An approval does not imply testing is done — check the task list explicitly.
48
63
49
64
### TeamCity Builds
50
65
@@ -62,10 +77,71 @@ Group suites into four categories (show non-empty categories only):
-**Pre-existing failures** (`fails_on_primary: true`) — not caused by this branch
64
79
- Tests with unknown primary-branch status
65
-
- Note if `has_newer_commits: true` — result may be outdated
66
-
3.**Passing** (`status: SUCCESS`, `state: finished`) — list with a stale warning if `has_newer_commits: true`
67
-
4.**Not Yet Triggered** (`status: NOT_STARTED`) — suites in the same sub-projects as known builds that have never run on this branch; list as a count with names
80
+
- If `has_newer_commits: true`, note which repos had newer commits (from `stale_repos`) — result may be outdated
81
+
3.**Passing** (`status: SUCCESS`, `state: finished`) — list with a stale note if `has_newer_commits: true`; for stale builds include which repos had newer commits (from `stale_repos`)
82
+
4.**Not Yet Triggered** (`status: NOT_STARTED`) — suites in the same sub-projects as known builds that have never run on this branch; show only the count, not the individual names
83
+
84
+
### Overall Assessment
85
+
86
+
End with a one-paragraph verdict: is this branch ready to merge? Factor in: PR approvals, CI/TC results (and whether they are current or stale), and PR task list completion. Call out any unchecked blocker tasks (manual test, automated test, etc.) as merge blockers even if the PR is already approved. Deferrable tasks (TeamCity verify and merge, user education handoff, etc.) should not block the verdict. If not ready, state specifically what needs to happen first.
Blockers: LabKey/targetedms — manual test not yet checked off.
111
+
112
+
---
113
+
114
+
### TeamCity Builds
115
+
116
+
**Failures** (1)
117
+
118
+
- MS2 sqlserver — 1 new failure (STALE: newer commits exist since build)
119
+
- org.labkey.test.tests.ms2.CometTest.testSteps
120
+
121
+
**Passing** — current (queued after latest commit 2026-05-18 21:07)
122
+
123
+
- Panorama [A] postgres
124
+
- Panorama [B] postgres
125
+
- Upgrade from 25.11
126
+
- Upgrade from 25.7
127
+
- Upgrade setup
128
+
- Upgrade validation
129
+
- build (Premium)
130
+
131
+
**Passing** — stale (queued before latest commit)
132
+
133
+
- BVT-EHR postgres
134
+
- BVT-EHR sqlserver
135
+
- MS2 Postgres
136
+
- Verify Java Build
137
+
- Verify Test Build
138
+
- build (Community)
139
+
- build_ehr
140
+
141
+
**Not Yet Triggered** (71 suites)
142
+
143
+
---
68
144
69
145
### Overall Assessment
70
146
71
-
End with a one-paragraph verdict: is this branch ready to merge? Factor in whether the shown results are current (`has_newer_commits`) or whether builds are still in progress. If not ready, state specifically what needs to happen first.
147
+
Not ready to merge. The LabKey/targetedms PR has an unchecked manual test task. The MS2 sqlserver suite also shows a new failure (CometTest) though that build is stale — it should be re-run after the latest commits before merging.
0 commit comments