Repository navigation
fix(devops-health): resilient dashboard issue discovery - #737
Merged
Merged
Conversation
The health check located its dashboard issue solely via the devops-health label search. When GitHub silently dropped the pinned dashboard (#288) from its issue search/list index, the workflow could not find it, created a duplicate (#695), and abandoned the pinned issue -- leaving the pinned dashboard stale for days. Step 4.1 now resolves the dashboard by a cached issue number first (updating it directly by number, which works even when the issue is missing from search), persists that number to cache-memory every run, falls back to label + pinned-issue lookup, and consolidates duplicates. Documents the new health-dashboard-issue cache key. Lock file unchanged: the prompt body is runtime-imported from these .md files.
JanKrivanek
marked this pull request as ready for review
June 9, 2026 15:26
JanKrivanek
enabled auto-merge (squash)
June 9, 2026 15:27
Contributor
There was a problem hiding this comment.
Pull request overview
Improves the DevOps Health Check workflow’s stability by ensuring it consistently finds and updates the same “Repository Health Dashboard” issue even when GitHub search/label indexing fails, preventing duplicate dashboard creation.
Changes:
- Updates Step 4.1 in the workflow prompt to resolve the dashboard issue by cached issue number first, then fall back to label/pinned discovery, and consolidate duplicates.
- Adds
health-dashboard-issueas a documentedcache-memorykey to persist the canonical dashboard issue number across runs. - Adds an explicit verification checklist item to avoid duplicating the dashboard due to empty label search results.
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/devops-health-check.md | Updates the workflow prompt to resolve/update the dashboard issue reliably (cached number first) and adds guidance to prevent duplicates. |
| .github/aw/shared/devops-health.lock.md | Documents the new cache-memory key used to persist the canonical dashboard issue number. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 2
AbhitejJohn
approved these changes
Jun 9, 2026
Contributor
|
👋 @JanKrivanek — this PR has 2 unresolved review thread(s). When you're ready, please address the feedback and push an update; the triage bot will pick up the next state automatically. (Add the |
…uest Address PR review feedback: - Validate the cached health-dashboard-issue before reusing it (open + devops-health label or expected title); treat 404/mismatch as a cache miss so the label/pinned fallback recovers safely instead of overwriting an unrelated issue. - Move the 'please pin' request inside the body template (below the status block) instead of above the required header, so it no longer conflicts with the documented body format or island replacement.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The health check found its dashboard issue only via the
devops-healthlabel search. When GitHub silently dropped the pinned dashboard (#288) from its search/list index, the workflow couldn't find it, created a duplicate (#695), and abandoned the pinned issue — leaving it stale for days.Step 4.1 now resolves the dashboard by a cached issue number first (updating it directly by number, which works even when the issue is missing from search), persists that number every run, falls back to label + pinned-issue lookup, and consolidates duplicates.
Lock file unchanged — the prompt is runtime-imported from these
.mdfiles.Live cleanup already applied: #695 pinned, #288 closed as duplicate.