Repository navigation
π₯ Repo Health Dashboard β dotnet/machinelearningΒ #7634
Description
π₯ Repo Health Dashboard β dotnet/machinelearning
Last updated: 2026-07-03 07:01 UTC Β· Run: #28644126447
| Status | Count |
|---|---|
| π΄ Critical | 0 |
| π‘ Warning | 7 |
| iοΈ Info | 2 |
| β Resolved (recent) | 1 |
| π Baselined | 3 |
Overall: π‘ Warning β stable from yesterday
π Executive Summary
The repo is holding at a Warning state for Day 23. No new critical findings. One new PR (#7652) was opened yesterday to isolate agentic workflow authentication using a Copilot token pool. All seven persistent warnings from prior runs are unchanged β the untriaged issue backlog, blocking-clean-ci cluster, stale community PRs, and agentic noise remain the dominant concerns.
AzDO pipeline monitoring (vsts-ci, codecoverage-ci, night-build, outer-loop-build) is disabled β
AZDO_PATnot configured.
π΄ Critical Findings
None.
π‘ Warning Findings
| ID | Category | Finding | Status | Age |
|---|---|---|---|---|
| I3-untriaged | Issue | 50+ untriaged open issues; agentic bot PRs adding noise | π EXISTING | Day 23 |
| I2-no-milestone | Issue | 821+ open issues without milestone β planning gap | π EXISTING | Day 23 |
| C5-blocking-ci-6978 | Pipeline | #6978 TorchSharp QA OOM (blocking-clean-ci) β updated again today |
π EXISTING | Day 18 |
| C6-blocking-ci-cluster | Pipeline | ~15 open blocking-clean-ci issues; count stable |
π EXISTING | Day 15 |
| P2-community-pr-7609 | PR | #7609 arm64 SymSGD community PR awaiting review β 59 days old | π EXISTING | Day 9 |
| INFO-agentic-noise | Issue | ci-scan-feedback bot loop: fallback issues accumulating in tracker |
π EXISTING | Day 6 |
| PR-7625-stale | PR | #7625 SentencePieceTokenizer Copilot PR awaiting human review β 23d since last update | π EXISTING | Day 4 |
iοΈ Info Findings
| ID | Category | Finding | Status | Age |
|---|---|---|---|---|
| PR-7652-new | PR | #7652 New: Isolate agentic auth with Copilot token pool (by @kotlarmilos) |
π NEW | Day 0 |
| PR-7626-review | PR | #7626 PredictionEnginePool hot-swap fix awaiting review β 19d old, recently active | π EXISTING | Day 4 |
β Recently Resolved
| ID | Category | Finding | Resolved |
|---|---|---|---|
| P5-stale-prs | PR | Stale bot PRs #7607 and #7570 actively maintained | 2026-06-20 |
π Baselined Findings
| ID | Finding |
|---|---|
| I1-P0-5805 | #5805 P0: MKLImports PDB missing β known tech debt |
| P5-stale-long-prs | #7416, #7406 long-lived PRs (TorchSharp, 4-bit quantization) |
π 7-Day Trends
| Metric | Value | Trend |
|---|---|---|
| Open Issues (total) | 821+ | β Stable |
| Untriaged Issues | 50+ | β Slow growth |
| Open PRs | ~17 | β +1 new (#7652) |
| blocking-clean-ci issues | ~15 | β Stable |
| backport.yml (last run) | β success | β Stable |
| locker.yml (run #945) | β success | β Stable |
| AzDO pipelines | N/A |
π Links
Note
π Integrity filter blocked 65 items
The following items were blocked because they don't meet the GitHub integrity level.
- #7610
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #7606
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #7605
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #7569
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #7094
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #6449
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Error: "Microsoft.ML currently supports 'x64' and 'x86' processor" when target runtime is *linux-arm* or *linux-arm64*Β #6588
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Exposing the tree for multiclass classificationΒ #6370
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - CreateEnumerable code fails in Visual Studio FSI but works in .NET Interactive notebook?Β #6353
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Add substitutes for 4 IntelMKL methods so SymSgd can be added to non x86/x64 buildsΒ #5798
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Memory leak Β #5744
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - Migrate to VSTest for all Unit TestsΒ #5587
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - OMP: Error #15: Initializing libiomp5.dylib in Image Classification with AutoMLΒ #5569
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - SVMLightLoader Fails above 128 dense rowsΒ #5566
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - TensorFlow scoring sample should pass an empty dataviewΒ #4210
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - mlnet's generated projects don't include the cs filesΒ #4145
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - ... and 49 more items
To allow these resources, lower min-integrity in your GitHub frontmatter:
tools:
github:
min-integrity: approved # merged | approved | unapproved | noneGenerated by Repo Health Check β Orchestrator Β· β 935.4K Β· β·
Activity
github-actions commentedon Jun 17, 2026
github-actions commentedon Jun 17, 2026
github-actions commentedon Jun 17, 2026
π Investigation:
I3-untriagedFinding: 221+ open issues with
untriagedlabel β triage process gap persisting for 7+ daysSeverity: Medium
Category: Issue
Evidence
221+ open issues carry
untriagedβ stable at this level for 7+ days per dashboard trend (count unchanged between 2026-06-10 and 2026-06-17). β Source: dashboard π₯ Repo Health Dashboard β dotnet/machinelearningΒ #7634untriagedlabel policy is milestone-driven β.github/policies/untriaged.ymladds the label on issue open/reopen when no milestone is assigned; removes it only when the issue is closed or assigned to a milestone. There is no time-based or activity-based removal. β Source:.github/policies/untriaged.ymlI3-untriagedandI2-no-milestoneare the same problem β the 221+ untriaged issues are a direct subset of the 821+ issues without a milestone. Adding any issue to a milestone automatically removesuntriaged. No milestone assignment =untriagedforever. β Source: policy logic + dashboardIssue triage agent adds but never removes
untriagedβ.github/workflows/issue-triage.agent.md(triggered onissues: [opened]) classifies new issues and always addsuntriagedalongside other labels. The prompt explicitly says "Always adduntriagedalongside any other label." Removal depends entirely on a human assigning a milestone. β Source:.github/workflows/issue-triage.agent.mdOldest visible untriaged issue: ~3 years old β Object detection: Enable loading from checkpoint Β #6670 created 2023-05-10 (
enhancement+needs-further-triage), never assigned a milestone. β Source: list_issues query (ASC by created_at)Known Build Error (Helix CI bot) issues inflate count β Issues like Failure to load lib_lightgbm in Microsoft.ML.Fairlearn.Tests.GridSearchTest.TestGridSearchTrialRunner2Β #6841, ArgumentOutOfRangeException when running Microsoft.ML.Fairlearn.Tests.GridSearchTest.TestGridSearchTrialRunner2Β #6842, Microsoft.ML.Tests.TrainerEstimators.TrainerEstimators.TestEstimatorMulticlassNaiveBayesTrainer failed with assertΒ #7060, AutoML tests writing test output outside of a test which causes test process to fail with no failing test casesΒ #7067 are auto-generated by Helix CI (
ericstjbot), carryuntriaged + blocking-clean-ci + Known Build Error, and are tracked in a separate AzDO system. They were bulk-touched today at 07:00 UTC but still carryuntriagedbecause no milestone is assigned. β Source: list_issues (updated_at DESC)Automated agentic workflow failure reports also get
untriagedβ [aw] CI Failure Scanner - Feedback (machinelearning) failedΒ #7633 (CI Failure Scanner failure, created today, auto-expires 2026-06-24) carriesuntriaged. These transient operational issues go through a different lifecycle but are counted in the backlog. β Source: list_issuesNo closed/resolved
untriagedissues in 2026 visible β A search forlabel:untriaged is:closed closed:>2026-01-01returned only agentic workflow failure reports (operational, not community issues). Zero community bug/featureuntriagedissues have been triaged closed this year. β Source: search_issuesActive feature work is happening on untriaged issues β [API] Public way to construct SentencePieceTokenizer (Unigram) from tokenizer.json / in-memory pieces+scoresΒ #7624 (
[API] Public way to construct SentencePieceTokenizer, created 2026-06-10) has an assignee (Copilot) and 6 comments, yet still carriesuntriagedsimply because no milestone was assigned. This shows the label is losing signal value. β Source: search_issuesRoot Cause
Confidence: High
The
untriagedlabel is mechanically equivalent to "no milestone assigned." The policy is working as designed β but no systematic milestone assignment process exists, so the label accumulates indefinitely. Three compounding factors worsen the backlog: (1) the oldest community issues have been awaiting triage for 2β3 years, (2) Helix CI and agentic workflow bots auto-create issues that immediately receiveuntriagedbut are managed through separate systems and never get milestones, and (3) theissue-triage.agent.mdintentionally preservesuntriagedbecause removing it requires a human milestone decision that never happens. This is a process gap, not a tooling failure.Recommendations
Known Build Error + blocking-clean-ciissues to a "Backlog" or "Tracking" milestone (or close as "won't fix" if stale). These are CI-bot-generated and managed in AzDO β they should not count as untriaged community issues. Approx 15β30 issues.[aw]title prefix oragentic-workflowslabel) from theuntriaged.ymlpolicy β they haveexpiresmarkers and don't need standard triage.untriagedcount while preserving planning flexibility.untriagedβ close stale/duplicate ones, assign the rest to a milestone. Focus on pre-2024 issues first (~50+ visible, more filtered by integrity).issue-triage.agent.mdto removeuntriagedwhen it determines an issue is aKnown Build Error(has Helix CI structure) or is an agentic workflow failure.untriagedolder than 180 days without activity should be auto-closed or auto-assigned to "Backlog" milestone β this prevents indefinite accumulation.Related
I2-no-milestoneis the same underlying gap β 821+ open issues without milestone).github/policies/untriaged.yml.github/workflows/issue-triage.agent.mduntriaged)Investigated by repo-health-investigate β’ Finding:
I3-untriagedNote
π Integrity filter blocked 92 items
The following items were blocked because they don't meet the GitHub integrity level.
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jun 18, 2026
github-actions commentedon Jun 18, 2026
github-actions commentedon Jun 19, 2026
github-actions commentedon Jun 19, 2026
github-actions commentedon Jun 20, 2026
github-actions commentedon Jun 21, 2026
github-actions commentedon Jun 22, 2026
π Health Delta β 2026-06-22 07:49 UTC
Changes since 2026-06-21:
blocking-clean-ci) updated by bot at 07:00 UTC today β ongoing, Day 7Severity: π‘ Warning (unchanged since 2026-06-11) | Dispatches: 0 / 5 budget used
Note
π Integrity filter blocked 58 items
The following items were blocked because they don't meet the GitHub integrity level.
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jun 23, 2026
π Health Check Delta β 2026-06-23
Run vs. previous: 2026-06-22 (#27937550540) β 2026-06-23 (#28008648004)
Key observations:
blocking-clean-ciissues still open and unchanged β 5 were auto-touched by CI bot at 07:02 UTC today: #6978, #7393, #7417, #7418, #7419untriagedlabel query timed out again (GitHub MCP WASM trap); count estimated β₯100 (consistent)AZDO_PATconfiguredOverall status: π‘ Warning β stable, no changes from prior run
Note
π Integrity filter blocked 65 items
The following items were blocked because they don't meet the GitHub integrity level.
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jun 24, 2026
π Health Check Delta β 2026-06-24T07:04Z
Findings summary:
P5-stale-long-prs)P5-stale-prsstill closed since 2026-06-20)Key changes since 2026-06-23:
blocking-clean-ciβ TorchSharp QA OOM) received CI bot activity at 07:00 UTC today β still open and blocking CI (Day 9)P5-stale-long-prs: PRs #7416 (TorchSharp 0.105.0 update, assigned@LittleLittleCloud, 450 days stale) and #7406 (GenAI 4-bit quantization, assigned@LittleLittleCloud, 470 days stale) β both targetingmain, no activity since March 2025blocking-clean-ciissues remain open (Day 7 for cluster finding)P5-stale-long-prs(new) +C5-blocking-ci-6978(active today)Severity:β οΈ Warning (no change from previous run)
Run #28081292211 Β· AzDO monitoring disabled (noβ οΈ Partial data: GitHub API WASM timeout on some queries
AZDO_PAT) Β·Note
π Integrity filter blocked 64 items
The following items were blocked because they don't meet the GitHub integrity level.
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jun 24, 2026
π Investigation:
P5-stale-long-prsFinding: PRs #7416 and #7406 on main have been stale for 450β470 days with no reviewer activity β evaluate closure or reassignment
Severity: Medium
Category: PR
Evidence
@LittleLittleCloud. State: open,mergeable_state: dirty(merge conflict with main). No CI check runs recorded.@LittleLittleCloud. State: open,mergeable_state: dirty. No CI check runs recorded.@LittleLittleCloud), with no author activity after March 2025.@michaelgsharpran CI and identified that TorchSharp β₯0.105.0 dropped OSX-x64 support. Additional work was needed to gate TorchSharp builds/tests away from OSX-x64. No follow-up from the author occurred after this was raised. Additionally, the current repoTorchSharpVersionis0.102.7β the proposed0.105.0is now 15+ months old and almost certainly obsolete.@michaelgsharpraised concerns on 2025-03-07/10 about introducing a new runtime dependency (LittleLittleCloud.TorchSharp.BitsAndBytes) owned by the PR author personally (not Microsoft/dotnet). The author confirmed personal ownership (MIT license). Reviewer also asked whether this could go into TorchSharp upstream and whether the version should be centrally pinned. Two review threads remain unresolved.Root Cause
Confidence: High
Both PRs stalled due to concrete blockers raised by reviewers that the author did not address. For #7416, a last-minute CI run revealed a platform incompatibility (OSX-x64 dropped in TorchSharp 0.105.0) requiring non-trivial extra work. For #7406, the reviewer raised a valid governance concern about adding a personally-maintained CUDA library as a repo dependency. In both cases the author went silent and the PRs aged into merge-conflict state with no CI coverage.
Recommendations
@michaelgsharp)LittleLittleCloud.TorchSharp.BitsAndBytesdependency governance question was never resolved, and the PR has diverged from main. Close with a comment inviting the author to reopen after (a) resolving the dependency ownership concern or (b) proposing an alternative approach that avoids a personally-owned CUDA package.@michaelgsharp)actions/stale) to warn and auto-close PRs with no activity for 90β120 days. This prevents accumulation of conflicted, CI-dark PRs.Related
Investigated by repo-health-investigate β’ Finding:
P5-stale-long-prsNote
π Integrity filter blocked 1 item
The following item was blocked because it doesn't meet the GitHub integrity level.
search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:3 remaining items
github-actions commentedon Jun 26, 2026
π Daily Delta β 2026-06-26
Run: #28223027704 Β· Compared to: 2026-06-25
No changes since yesterday. All four warning findings remain at existing status:
blocking-clean-cicluster holds at 15 open issues β no change.GitHub Actions CI: backport.yml β Β· locker.yml β (all recent runs successful)
AzDO pipeline monitoring: disabled β
AZDO_PATnot configured.Note
π Integrity filter blocked 118 items
The following items were blocked because they don't meet the GitHub integrity level.
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jun 27, 2026
π Health Check Delta β 2026-06-27
Changes since 2026-06-26
AZDO_PAT)Note
π Integrity filter blocked 126 items
The following items were blocked because they don't meet the GitHub integrity level.
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jun 28, 2026
π Daily Delta β 2026-06-28T07:15 UTC
No change from yesterday's scan. Repo remains at π‘ Warning.
Notable updates
blocking-clean-ciTorchSharp QA OOM) received another activity update at 07:00 UTC today β Day 13 tracked, issue remains open and unresolvedblocking-clean-cicluster holds at exactly 15 issues for Day 10 β no new closures overnightINFO-issue-7645(bot ci-scan-feedback noise) transitions: π NEW β π EXISTING (Day 1)No dispatches triggered
No new π΄ Critical or π NEW π‘ Warning findings β investigator dispatch budget unused (0/5).
Workflow Run #28314810056
Note
π Integrity filter blocked 142 items
The following items were blocked because they don't meet the GitHub integrity level.
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jun 29, 2026
π Health Check Delta β 2026-06-29 07:31 UTC
Run: #28355875362 | Status: π‘ Warning (stable)
Changes since 2026-06-28
π New Findings
PR-7625-stale: PR #7625 β Copilot-generated SentencePieceTokenizer API PR has been open 19 days without review or merge. Copilot PRs require human review; this is blocking a tokenizer API improvement.PR-7626-review: PR #7626 β Community contribution fixing memory leak + stale-model issue inPredictionEnginePoolhot-swap, 15 days old, assigned tokotlarmilos.π Notable Existing Findings
blocking-clean-ci) updated again at 07:00 UTC today (Day 14 of tracking)blocking-clean-cicluster β Stable at 15 issues (Day 11); no new issues added or resolvedKey Metrics
blocking-clean-cicountπ Dispatched Investigations (1 of 5)
PR-7625-stale(π‘ Warning, NEW) β Copilot PR awaiting review 19+ daysNote
π Integrity filter blocked 85 items
The following items were blocked because they don't meet the GitHub integrity level.
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jun 29, 2026
π Investigation:
PR-7625-staleFinding: Copilot PR #7625 (SentencePieceTokenizer APIs) awaiting review 19 days without merge
Severity: High
Category: PR
Evidence
mergeable_state: "blocked"β PR cannot be merged in its current state β GitHub API responseMachineLearning-CIaggregate: β FAILURE; specificallyMachineLearning-CI (MacOS_cross_arm64 Release_Build)β FAILURE; Windows cross-arm64 builds β CANCELLED β check runs on commite1ff3c5cstate: "COMMENTED"; noAPPROVEDorCHANGES_REQUESTEDfrom any maintainer β reviews APIericstjβ Identified two correctness bugs in initial review (2026-06-11): (a) BOS/EOS positional fallback corrupts real vocab pieces when<s>/</s>are absent, (b)ExtractPrecompiledCharsMapsilently drops sibling normalizer steps instead of throwing β review comment #4472717485@copilotplease address feedback" β ericstj re-triggered Copilot iteration on 2026-06-18 (comment #4676096355); Copilot pushed multiple commits that dayRoot Cause
Confidence: High
The PR is dually blocked: the CI is failing on MacOS cross-arm64 (the only non-cancelled platform build that failed, suggesting a test or platform-specific issue introduced by or not covered by the new tokenizer test fixtures), and no human reviewer has issued a formal approval.
ericstjis actively engaged but has not approved β likely waiting for CI to go green and/or for the remaining review thread items to be fully addressed. The Copilot author cannot self-merge without human sign-off, and the last push (2026-06-18) left CI broken, stalling the loop.Recommendations
1471203for the specific test failure log; determine if it is a flaky infra issue or a real test failure caused by PR changesericstj/ any maintainer@copilotwith specific instructions to fix the failing test/codeericstjericstj(or another maintainer) should issue a formal review decision (APPROVED or CHANGES_REQUESTED) to unblock mergeericstjericstjSequencenormalizers to prevent regressionsRelated
MachineLearning-CI (MacOS_cross_arm64 Release_Build)β run ID 82204245413@ericstj(MEMBER, active)Investigated by repo-health-investigate β’ Finding:
PR-7625-stalegithub-actions commentedon Jun 30, 2026
π Health Check Delta β 2026-06-30T07:11 UTC
vs previous run (2026-06-29)
Key changes:
ci-scan.agent.mdneeds Hard Rule 10 to enforce early-exit on skip-only runs. Action needed: apply the patch from [ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7648 or close these issues as noise once fixed.infoβwarning(13 issues, escalating pattern).NEWβEXISTING(Day 1). Now 20 days old, assigned to@ericstj.NEWβEXISTING(Day 1). Now 16 days old.Overall status: π‘ Warning β no change from previous run. No new critical findings.
Run #28426815194 Β· AzDO monitoring disabled (no
AZDO_PAT)Note
π Integrity filter blocked 53 items
The following items were blocked because they don't meet the GitHub integrity level.
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jun 30, 2026
π Investigation:
INFO-agentic-noiseFinding: ci-scan-feedback bot filing 13 consecutive fallback issues (#7627β#7648) β failed PR-to-issue fallback loop
Severity: High
Category: Issue
Evidence
stale build window (>14d)since 2026-06-08 β the most recent failed AzDO build (#1453653) is now 22+ days old, so every run correctly skips. β Source: [ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7648 bodyci-scan.agent.mdlines 80β92 have Hard Rules 1β9, but the early-exit instruction only appears inside Step 1 prose as "and stop". On some runs agents continue past it to Steps 2β7, fetching AzDO timelines, task logs, and Helix data that serve no purpose. β Source:ci-scan.agent.mdSHA0937c5f| 0 | 0 | 0 | 0 |instead of| 0 | 0 | 0 | 1 |β the skipped count is not reflected in structured output because Step 7 tally is never reached. β Source: [ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7648 body.github/workflows/ci-scan.agent.md, elevating the early-exit to the same level as the issue-cap and label invariants. The full ready-to-apply patch (57 lines) is in [ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7648. β Source: [ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7648 body, patch previewRoot Cause
Confidence: High
There are two layered bugs, both with clear evidence:
Bug 1 (Content) β
ci-scan.agent.mdis missing Hard Rule 10. The early-exit on "no scannable build" lives only in Step 1 prose ("and stop"), which some model runs interpret permissively, causing them to proceed through Steps 2β7 and waste 10Γ tokens. The tally is also wrong on skip-only runs.Bug 2 (Infrastructure) β
ci-scan-feedback's git push is failing on every run. The bot correctly identifies the fix and generates a valid patch, but cannot push a branch to create a PR. The PR-to-issue fallback fires instead, creating a new duplicate issue on every daily run. The bot does not deduplicate against its own prior fallback issues, so the flood continues indefinitely.Recommendations
.github/workflows/ci-scan.agent.mdafter Rule 9 β a 2-line change. This fixes the content bug and stops future ci-scan over-runs.git pushis failing. Likely cause: branch protection requiring PRs, or the workflow token lackscontents: write. Check the workflow run logs for runs 27523314204 β 28419478972 for the push error.contents: writescoped to the agent branch namespace only.Proposed Hard Rule 10 (ready to apply)
Add this line to
.github/workflows/ci-scan.agent.mdafter Rule 9:Also update the Step 1 trailing sentence to read:
"If selection yields no scannable build, apply Hard Rule 10 immediately."Full patch with both changes is in #7648.Related
.github/workflows/ci-scan.agent.md(SHA0937c5f)Investigated by repo-health-investigate β’ Finding:
INFO-agentic-noisegithub-actions commentedon Jul 1, 2026
π Daily Delta β 2026-07-01T07:22 UTC
Run: #28500685308 Β· compared to run 2026-06-30
Notable changes:
blocking-clean-ciTorchSharp QA OOM) was updated at 07:00 UTC today β renewed activity on this known CI blocker@ericstjNo new dispatches β all warning findings have existing investigation issues.
Note
π Integrity filter blocked 160 items
The following items were blocked because they don't meet the GitHub integrity level.
list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jul 2, 2026
π₯ Repo Health Delta β 2026-07-02
Run: #28571700375 Β· vs. previous run 2026-07-01
Key Changes
blocking-clean-ciissues unchanged; #6978, #7418, #7419 all updated today by Arcade health checks.Dispatched Investigators
AzDO monitoring: Disabled β configure
AZDO_PATsecret to enable pipeline health data.GitHub Actions CI: β All healthy (backport + locker).
Note
π Integrity filter blocked 45 items
The following items were blocked because they don't meet the GitHub integrity level.
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jul 2, 2026
π Investigation:
INFO-agentic-noiseFinding: ci-scan-feedback bot loop β 95 consecutive skipped ci-scan runs producing fallback issues at ~1/day since Jun 8 (latest: #7651)
Severity: High
Category: Issue
Evidence
95 consecutive ci-scan skips (Jun 8 β Jul 2) β Every 6h run of
ci-scanexits at Step 1 withstale build window (>14d): AzDOMachineLearning-CIdefinition 167 onmainhas had no builds within the 14-day scannable window since the workflow launched. Source: [ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7651 body, [ci-scan-feedback] ci-scan: add Hard Rule 10 for early exit on no scannable buildΒ #7627 body, dashboard π₯ Repo Health Dashboard β dotnet/machinelearningΒ #7634.14+ fallback issues filed, zero PRs ever created β
ci-scan-feedbackcorrectly detects the skip-path token waste, proposes adding Hard Rule 10 toci-scan.agent.md, attemptscreate_pull_request, but every push fails with "the git push operation failed" and falls back to filing an issue instead. Confirmed: 0 open[ci-scan-feedback]PRs exist. Source: issues [ci-scan-feedback] ci-scan: add Hard Rule 10 for early exit on no scannable buildΒ #7627, [ci-scan-feedback] ci-scan: add Hard Rule 10 for early exit on no scannable buildΒ #7630, [ci-scan-feedback] ci-scan: add Hard Rule 10 to force early exit on no scannable buildΒ #7636β[ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7648, [ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7650, [ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7651; GitHub PR search.All 14+ fallback issues propose the same 2-line patch β Hard Rule 10 adds an explicit early-exit invariant to
ci-scan.agent.md(append skip reason, print| 0 | 0 | 0 | 1 |, emitnoop, stop β without fetching AzDO timeline/logs/Helix). The patch is functionally identical in every fallback issue. Source: comparing [ci-scan-feedback] ci-scan: add Hard Rule 10 for early exit on no scannable buildΒ #7627, [ci-scan-feedback] ci-scan: add Hard Rule 10 for early exit on no scannable buildΒ #7630, [ci-scan-feedback] ci-scan: add Hard Rule 10 for explicit early exit on no scannable buildΒ #7651 diffs.ci-scan.agent.mdonmainstill unpatched β SHA0937c5f, Hard Rule 10 absent, file unchanged since initial merge. The fix proposed daily since Jun 15 has never landed. Source:github-get_file_contents.PR [ci-scan-feedback] Fix push to existing feedback PR on scheduled runsΒ #7620 (merged Jun 9) fixed the wrong code path β It fixed
push-to-pull-request-branch(updating an existing PR) but leftcreate-pull-request(creating the first PR) broken. Since no PR has ever been successfully created, every daily run sees "no existing PR" β triescreate_pull_requestβ push fails β new fallback issue. Source: [ci-scan-feedback] Fix push to existing feedback PR on scheduled runsΒ #7620 body.Workflow runs succeed despite push failure β All 5 jobs in run
28564527554(Jul 2) concludedsuccess; the gh-aw runtime handles push failures gracefully by creating a fallback issue. The noise is a design artifact, not a workflow crash. Source:list_workflow_jobs.Exact push error not surfaced in available logs β The gh-aw safe-outputs server emits a generic fallback message. The workflow declares
permissions: read-allon the agent job; if the safeoutputs runtime relies on the GITHUB_TOKEN rather than the Copilot App token for branch creation, the missingcontents: writescope would explain the consistent failure from day one of proposals.Root Cause
Confidence: High
Two co-occurring issues form a feedback loop. (A)
MachineLearning-CI(AzDO definition 167) has had no builds within the 14-day scan window since June 8, so everyci-scanrun skips at Step 1; the existing "and stop" prose instruction is not a hard constraint and some model versions continue to fetch timelines/logs before concluding the skip (250Kβ5.8M effective-token variance per run). (B)ci-scan-feedbackcorrectly diagnoses this and proposes Hard Rule 10 each day, butcreate-pull-requestfails every time β most likelypermissions: read-allon the agent job prevents branch push if the safeoutputs server uses the GITHUB_TOKEN, or the Copilot App's installation token lacks write access to this repo. Because no PR is ever created, every daily run re-proposes the same fix and creates a new fallback issue, flooding the tracker at ~1/day.Recommendations
gh run download <run-id> -n agent, thengit am --3way, push, PR. This stops the daily fallback flood once Hard Rule 10 lands.create-pull-requestpush failure inci-scan-feedback. Addcontents: write(andworkflows: writeif needed) to the agent job'spermissionsblock and re-test via manual workflow dispatch. Compare withdotnet/runtime's equivalent workflow if that one is creating PRs successfully.MachineLearning-CIdefinition 167 has had no builds accessible in 24+ days β pipeline disabled, frequency drop, or scan window needs recalibration.ci-scan-feedbackfallback: skip filing a new fallback issue if an open issue with the same title stem was filed within the last 7 days with no action taken.Related
.github/workflows/ci-scan.agent.md(SHA0937c5f)Investigated by repo-health-investigate β’ Finding:
INFO-agentic-noisegithub-actions commentedon Jul 2, 2026
π Investigation:
P2-community-pr-7609Finding: Community PR #7609 β Enable SymSgdNative on arm64 via system BLAS (fixes #5798)
Severity: Medium
Category: PR
Evidence
@anicka-net(community contributor); zero review comments; no assigned reviewers, no milestone β PR #7609Ubuntu_x64_cross_arm Debug/Release,Ubuntu_x64_cross_arm64 Debug/Release,Windows_cross_arm64 Debug/Release,MacOS_cross_arm64 Debug/Release. All native x64 builds pass.find_package(BLAS REQUIRED)halting the build immediately when BLAS cannot be found in the cross-compilation sysroot.MklImportsArm/CMakeLists.txtusesfind_package(BLAS REQUIRED)β In CI cross-compilation environments (x64 host compiling for ARM target), ARM BLAS libraries (OpenBLAS) are not installed in the x86 sysroot and CMake'sfind_packagedoes not search the target sysroot unless explicitly configured.Root Cause
Confidence: High
The PR correctly fixes arm64 native support by replacing Intel MKL (x86-only) with an OpenBLAS-backed shim and sparse BLAS implementations in C. However, the new
MklImportsArm/CMakeLists.txtcallsfind_package(BLAS REQUIRED), which fails in all CI cross-compilation jobs (x64 host β ARM target) because the cross-compilation sysroot does not have ARM-architecture BLAS libraries installed, and CMake does not automatically search the target sysroot. The PR was validated only on a native ARM64 machine where OpenBLAS is available natively. The CI has no native ARM64 runners, so the cross-compilation failure was not caught pre-submission.Recommendations
find_package(BLAS REQUIRED)βfind_package(BLAS)with a graceful skip/stub fallback or installlibopenblas-dev:arm64in the CI cross-compilation Docker image@anicka-net/ ML.NET teamUbuntu_arm64runner) to validate arm64-specific changes without relying on cross-compilationRelated
Ubuntu_x64_cross_arm*,Windows_cross_arm64,MacOS_cross_arm64Investigated by repo-health-investigate β’ Finding:
P2-community-pr-7609Note
π Integrity filter blocked 2 items
The following items were blocked because they don't meet the GitHub integrity level.
issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:github-actions commentedon Jul 3, 2026
π Daily Health Delta β 2026-07-03
Run: #28644126447 Β· Overall: π‘ Warning (unchanged)
Changes since 2026-07-02
π New Finding
@kotlarmilos: Isolate agentic workflow authentication with a Copilot token pool. New PR targeting thecopilot-pat-poolenvironment setup.Key Metric Changes
Notable Activity
No investigator dispatches β no new critical findings or severity escalations.
Note
π Integrity filter blocked 65 items
The following items were blocked because they don't meet the GitHub integrity level.
list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".list_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter: