fix: apply tracker:durable label when creating/updating weekly metrics tracker issue by stranske · Pull Request #2738 · stranske/Workflows

stranske · 2026-07-09T09:13:57Z

Summary

agents-weekly-metrics.yml created the "Agent metrics weekly summary" tracker issue without any labels, leaving it invisible to triage/stale-scan filters that key on tracker:durable. This was noted as a pre-existing gap in the review of PR 2737.

What changed

agents-weekly-metrics.yml and templates/consumer-repo/.github/workflows/agents-weekly-metrics.yml:

On creation: add labels: ['tracker:durable', 'automated'] to the issues.create call so new tracker issues are correctly tagged from the start.
On update (existing issue found): check whether tracker:durable is present and add it if missing — retroactively fixes issues created before this change (e.g. issue 2211).
Label normalization: use (target.labels || []).some(l => (typeof l === 'string' ? l : l?.name) === 'tracker:durable') (matching the sync_tracker_state/index.js pattern) to handle both label-object and label-string API shapes safely.

Also changed

config/template-drift-allowlist.txt: rebaselined the agents-weekly-metrics.yml fingerprint pair (pair.15) with new SHA256 values after the label fix. Root and template differ intentionally — do not align.

…s issue agents-weekly-metrics.yml created the tracker issue without labels, leaving it invisible to triage/stale-scan filters that key on tracker:durable. - On creation: pass labels: ['tracker:durable', 'automated'] so new issues are correctly tagged from the start. - On update (existing issue found): check for tracker:durable and add it if missing, retroactively fixing issues created before this change (e.g. #2211). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BrBgrJKcJvaucLF5sJKXHE

coderabbitai · 2026-07-09T09:14:05Z

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 39 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 4eebd561-4641-41f9-934d-666c125cf222

📥 Commits

Reviewing files that changed from the base of the PR and between 8889337 and 7e29861.

📒 Files selected for processing (3)

.github/workflows/agents-weekly-metrics.yml
config/template-drift-allowlist.txt
templates/consumer-repo/.github/workflows/agents-weekly-metrics.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch fix/weekly-metrics-tracker-durable-label

_{Comment @coderabbitai help to get the list of available commands.}

Mirror the agents-weekly-metrics.yml label fix in the consumer template to keep root and template in sync and clear the template-drift check. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BrBgrJKcJvaucLF5sJKXHE

agents-workflows-bot · 2026-07-09T09:15:52Z

Automated Status Summary

Head SHA: 7337ee1
Latest Runs: ⏳ pending — Gate
Required contexts: Gate / gate, Health 45 Agents Guard / guard
Required: core tests (3.12): ⏳ pending, core tests (3.13): ⏳ pending, docker smoke: ⏳ pending, gate: ⏳ pending

Workflow / Job	Result	Logs
(no jobs reported)	⏳ pending	—

Coverage Overview

Coverage history entries: 0

Updated automatically; will refresh on subsequent CI/Docker completions.

Keepalive checklist

Scope

Tracking issue for weekly agent workflow metrics.

Agent Metrics Summary

Generated: 2026-06-01T08:00:46Z
Records: 50 (keepalive 29, autofix 0, verifier 0, terminal dispositions 6, verifier follow-up ledgers 1, codex CLI freshness 1, autopilot 0, unknown 13)
Parse errors: 0
Range: 2026-05-31T18:27:46.016000Z to 2026-06-01T02:32:14.260000Z

Keepalive

Context for Agent

Related Issues/PRs

Tasks

Runs: 29
PRs: 7
Avg iterations: 0.0
Stop reasons: missing-agent-label (15), upstream Gate succeeded (9), no pull request context on gate run (2), autofix disabled for this pull request (2), head SHA drifted since Gate started (1)
Actions: wait (15)
Gate conclusions: success (8), cancelled (5)
Tasks complete rate: 0.0% (0/29)

Acceptance criteria

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3a217e9a20

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

chatgpt-codex-connector · 2026-07-09T09:16:16Z

                repo,
                title,
                body: 'Tracking issue for weekly agent workflow metrics.\n\n' + body,
+                labels: ['tracker:durable', 'automated'],


Mirror weekly metrics label fix into the consumer template

Because .github/sync-manifest.yml declares agents-weekly-metrics.yml as a consumer-managed workflow and a template copy exists at templates/consumer-repo/.github/workflows/agents-weekly-metrics.yml, this root-only label change leaves newly scaffolded consumer repos still creating/updating the weekly tracker without tracker:durable. In the consumer-template context, the stale-scan/triage filters that this patch is meant to satisfy will continue to miss the tracker, so please mirror the label creation/update logic into the template as well.

Useful? React with 👍 / 👎.

Done — commit 542ef79 applied the identical label fix to templates/consumer-repo/.github/workflows/agents-weekly-metrics.yml. The latest commit (7e29861) also normalizes the target.labels check (string vs object) and rebaselines the template-drift allowlist fingerprints.

Generated by Claude Code

Copilot

Pull request overview

Ensures the weekly “Agent metrics weekly summary” tracking issue is consistently discoverable by triage/stale-scan automation by applying the tracker:durable label (and automated on creation) from within the weekly metrics workflow.

Changes:

Add labels: ['tracker:durable', 'automated'] when creating the weekly metrics tracker issue.
When updating an existing tracker issue, add tracker:durable if it’s missing.

stranske · 2026-07-09T09:18:57Z

                repo,
                title,
                body: 'Tracking issue for weekly agent workflow metrics.\n\n' + body,
+                labels: ['tracker:durable', 'automated'],
              }));


Already mirrored in commit 542ef79. The latest commit (7e29861) additionally normalizes the target.labels check and rebaselines the template-drift allowlist so the Check Template Drift CI job passes.

Generated by Claude Code

stranske · 2026-07-09T09:18:58Z

                issue_number: target.number,
                body,
              }));
+              const hasLabel = target.labels.some(l => l.name === 'tracker:durable');


Fixed in 7e29861 — both root and template now use the pattern from sync_tracker_state/index.js:23-27: (target.labels || []).some(l => (typeof l === 'string' ? l : l?.name) === 'tracker:durable')

Generated by Claude Code

…wlist - Normalize the tracker:durable label check to handle both object and string label formats (per sync_tracker_state/index.js pattern): (target.labels || []).some(l => (typeof l === 'string' ? l : l?.name) === ...) Applied to both root and consumer template copies. - Rebaseline config/template-drift-allowlist.txt pair.15 with the new SHA256 fingerprints after the label fix. Root and template files differ intentionally (template SHA-pins actions + App token; root uses floating tags + coverage monitoring). Do not align. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01BrBgrJKcJvaucLF5sJKXHE

Copilot AI review requested due to automatic review settings July 9, 2026 09:13

stranske temporarily deployed to agent-high-privilege July 9, 2026 09:14 — with GitHub Actions Inactive

Copilot started reviewing on behalf of stranske July 9, 2026 09:14 View session

chatgpt-codex-connector Bot reviewed Jul 9, 2026

View reviewed changes

stranske temporarily deployed to agent-high-privilege July 9, 2026 09:16 — with GitHub Actions Inactive

Copilot AI reviewed Jul 9, 2026

View reviewed changes

stranske temporarily deployed to agent-high-privilege July 9, 2026 09:18 — with GitHub Actions Inactive

stranske merged commit 8ae71a9 into main Jul 9, 2026
86 checks passed

stranske deleted the fix/weekly-metrics-tracker-durable-label branch July 9, 2026 09:52

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

fix: apply tracker:durable label when creating/updating weekly metrics tracker issue - #2738

fix: apply tracker:durable label when creating/updating weekly metrics tracker issue#2738
stranske merged 3 commits into
mainfrom
fix/weekly-metrics-tracker-durable-label

stranske commented Jul 9, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot commented Jul 9, 2026 •

edited

Loading

Review limit reached

Uh oh!

agents-workflows-bot Bot commented Jul 9, 2026 •

edited by stranske-keepalive Bot

Loading

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Jul 9, 2026

Uh oh!

stranske Jul 9, 2026

Uh oh!

Copilot AI left a comment

Uh oh!

stranske Jul 9, 2026

Uh oh!

stranske Jul 9, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

stranske commented Jul 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

What changed

Also changed

Uh oh!

coderabbitai Bot commented Jul 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review limit reached

Uh oh!

agents-workflows-bot Bot commented Jul 9, 2026 • edited by stranske-keepalive Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Automated Status Summary

Coverage Overview

Keepalive checklist

Scope

Agent Metrics Summary

Keepalive

Context for Agent

Related Issues/PRs

Tasks

Acceptance criteria

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Jul 9, 2026

Choose a reason for hiding this comment

Uh oh!

stranske Jul 9, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

stranske Jul 9, 2026

Choose a reason for hiding this comment

Uh oh!

stranske Jul 9, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

stranske commented Jul 9, 2026 •

edited

Loading

coderabbitai Bot commented Jul 9, 2026 •

edited

Loading

agents-workflows-bot Bot commented Jul 9, 2026 •

edited by stranske-keepalive Bot

Loading