Skip to content

feat: implement issue #330 — [Fleet Monitor] petry-projects/.github — dev-lead.yml#421

Merged
don-petry merged 6 commits into
mainfrom
dev-lead/issue-330-20260609-0441
Jun 10, 2026
Merged

feat: implement issue #330 — [Fleet Monitor] petry-projects/.github — dev-lead.yml#421
don-petry merged 6 commits into
mainfrom
dev-lead/issue-330-20260609-0441

Conversation

@don-petry

Copy link
Copy Markdown
Contributor

Closes #330

Implemented by dev-lead agent. Please review.

@don-petry don-petry requested a review from a team as a code owner June 9, 2026 04:48
Copilot AI review requested due to automatic review settings June 9, 2026 04:48
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@coderabbitai

coderabbitai Bot commented Jun 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@don-petry, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 45 minutes and 38 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: a4ab4f1f-fc12-4d4d-84ff-d22462dcb143

📥 Commits

Reviewing files that changed from the base of the PR and between e79ae53 and c177300.

📒 Files selected for processing (1)
  • standards/ci-standards.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dev-lead/issue-330-20260609-0441

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

@don-petry don-petry enabled auto-merge (squash) June 9, 2026 04:49

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the CI standards documentation to specify that GH_PAT must be a fine-grained PAT and introduces a comprehensive failure-mode runbook for handling degraded dev-lead.yml stubs. The review feedback suggests a minor spelling correction from 'centralised' to 'centralized' to maintain consistency with the spelling conventions used throughout the rest of the document.

Comment thread standards/ci-standards.md Outdated
@don-petry don-petry disabled auto-merge June 9, 2026 04:49

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the org CI standards documentation to improve triage and remediation for Fleet Monitor “DEGRADED” alerts on the dev-lead.yml Tier‑1 workflow stub, reducing time spent debugging issues that actually live in the reusable workflow or external dependencies.

Changes:

  • Clarifies that GH_PAT for the Copilot engine must be a fine-grained PAT (classic ghp_* tokens fail at runtime).
  • Adds a “Failure-mode runbook” mapping common failing-run log signatures to likely root causes and where to apply fixes.
  • Documents why high cancellation counts are expected due to the reusable’s concurrency lane design.

Comment thread standards/ci-standards.md Outdated
coderabbitai[bot]
coderabbitai Bot previously approved these changes Jun 9, 2026
@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — fix-reviews (applied)

Changes committed and pushed.

@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

@don-petry don-petry enabled auto-merge (squash) June 9, 2026 04:51
@don-petry don-petry disabled auto-merge June 10, 2026 12:40
@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — review-changes (no-changes)

No changes were needed for this PR.

@don-petry don-petry enabled auto-merge (squash) June 10, 2026 12:41

@donpetry-bot donpetry-bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Automated review — APPROVED ✓

Risk: LOW
Reviewed commit: 383cbd9ee7b4d8f580ceac3bb3bf2b9a591a8692
Review mode: triage-approved (single reviewer)

Summary

Docs-only change to standards/ci-standards.md (+24/-1) that addresses Fleet Monitor issue #330 (dev-lead.yml WARNING, 15.5% failure rate). Annotates the GH_PAT secrets-table row to clarify classic ghp_ tokens are rejected at runtime, and adds a 'Failure-mode runbook' section mapping common failing-run log signatures to root causes and the repo where the fix belongs. The stance — fix upstream (reusable / external secret) rather than editing Tier-1 stubs — is consistent with the byte-equivalence contract already documented in this file.

Linked issue analysis

Issue #330 is a generic Fleet Monitor WARNING (failure rate > 10%, p95 632s, 48 cancelled runs). The PR does not change dev-lead.yml itself — instead it documents the triage path (why cancellations are expected from per-lane cancel-in-progress: false, which log signatures map to which upstream fix). Given that Tier-1 stubs must remain byte-equivalent across repos, a documentation runbook is a reasonable resolution; the PR body explicitly Closes #330 and the body of the runbook tells future triagers to close such Fleet Monitor issues by linking to the upstream fix rather than editing the stub.

Findings

  • No code, workflow, secret, or dependency changes — pure markdown documentation under standards/.
  • Gemini left one non-blocking style suggestion (centralised → centralized); the rendered diff already shows 'centralized', and the dev-lead fix-reviews bot ran successfully (sha d4c8c98) followed by a 'no-changes' confirmation at HEAD (sha 383cbd9). No unresolved reviewer threads.
  • CodeRabbit review was dismissed due to rate-limit, not a substantive objection.
  • mergeStateStatus is BEHIND main but mergeable=true; a base-branch update at merge time is sufficient — not a review blocker.
  • Content is internally consistent with the rest of ci-standards.md (concurrency lane design, engine-fallback cascade, fine-grained PAT requirement).

CI status

All required checks green: AgentShield, CI (Lint, ShellCheck, Agent Security Scan, Secret scan/gitleaks), CodeQL (actions), SonarCloud (Quality Gate passed, 0 new issues), Dev-Lead dispatch, PR Auto-Review ready-check. Audit/dependabot jobs SKIPPED as expected for a docs-only diff. No failing checks.


Reviewed automatically by the PR-review agent (single-reviewer mode: opus 4.7). Reply if you need a human review.

@don-petry don-petry disabled auto-merge June 10, 2026 13:34
@don-petry

Copy link
Copy Markdown
Contributor Author

Dev-Lead — waiting on PR blockers (intent: review-changes)

PR: #421
No changes were committed, but the PR still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews). The retry cron will re-attempt automatically. Next attempt after: 2026-06-10T14:05:40Z

@don-petry

Copy link
Copy Markdown
Contributor Author

Note

@don-petry I reviewed this PR and no code changes were needed, but it still has blocking checks or reviews (failing or cancelled checks, or changes-requested reviews), so I cannot mark it done yet. I'll re-check automatically.
Next attempt after: 2026-06-10T14:05:40Z

@don-petry don-petry enabled auto-merge (squash) June 10, 2026 13:35
@sonarqubecloud

Copy link
Copy Markdown

@don-petry don-petry merged commit cb11220 into main Jun 10, 2026
21 checks passed
@don-petry don-petry deleted the dev-lead/issue-330-20260609-0441 branch June 10, 2026 13:53
don-petry added a commit that referenced this pull request Jun 11, 2026
… dev-lead.yml (#421)

* feat: implement issue #330 — [Fleet Monitor] petry-projects/.github — dev-lead.yml

* fix(reviews): address review comments [skip ci-relay]

---------

Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com>
Co-authored-by: Don Petry Bot <donpetry+bot@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Fleet Monitor] petry-projects/.github — dev-lead.yml

3 participants