Skip to content

feat: implement issue #342 — [Fleet Monitor] petry-projects/.github-private — lint.yml - #524

Merged
don-petry merged 4 commits into
mainfrom
dev-lead/issue-342-20260609-2108
Jun 10, 2026
Merged

feat: implement issue #342 — [Fleet Monitor] petry-projects/.github-private — lint.yml#524
don-petry merged 4 commits into
mainfrom
dev-lead/issue-342-20260609-2108

Conversation

@don-petry

Copy link
Copy Markdown
Collaborator

Closes #342

Implemented by dev-lead agent. Please review.

Copilot AI review requested due to automatic review settings June 9, 2026 21:20
@don-petry
don-petry requested a review from a team as a code owner June 9, 2026 21:20
@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 6 minutes and 47 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: ea8d55da-2de0-4f39-9451-c239595e742e

📥 Commits

Reviewing files that changed from the base of the PR and between 19a235a and 0561564.

📒 Files selected for processing (1)
  • .github/workflows/lint.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dev-lead/issue-342-20260609-2108

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.

@gemini-code-assist

Copy link
Copy Markdown

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@don-petry

Copy link
Copy Markdown
Collaborator 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 21:23

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

This PR targets issue #342 by adjusting the repo’s lint workflow behavior, primarily around ShellCheck execution, with an additional (unrelated) tweak to the CI Failure Analyst agentic workflow trigger configuration.

Changes:

  • Updated .github/workflows/lint.yml ShellCheck invocation to use -x and globbed script paths.
  • Updated .github/workflows/ci-failure-analyst.md to add a branches: ["**"] filter under workflow_run.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/lint.yml Broadens and changes how ShellCheck is executed (adds -x, switches from explicit file list to globs).
.github/workflows/ci-failure-analyst.md Adds a branch filter to the workflow_run trigger configuration.

Comment thread .github/workflows/lint.yml Outdated
Comment thread .github/workflows/ci-failure-analyst.md Outdated
@don-petry
don-petry disabled auto-merge June 9, 2026 21:26
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — review-changes (applied)

Changes committed and pushed.

@don-petry
don-petry enabled auto-merge (squash) June 9, 2026 21:29
coderabbitai[bot]
coderabbitai Bot previously approved these changes Jun 9, 2026
@don-petry
don-petry disabled auto-merge June 9, 2026 21:32
@don-petry

Copy link
Copy Markdown
Collaborator 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-09T22:06:13Z

@don-petry
don-petry enabled auto-merge (squash) June 9, 2026 21:36
@don-petry
don-petry disabled auto-merge June 9, 2026 23:44
@don-petry

Copy link
Copy Markdown
Collaborator Author

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

PR: #524
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-10T00:17:02Z

@don-petry
don-petry enabled auto-merge (squash) June 9, 2026 23:47
@don-petry
don-petry disabled auto-merge June 9, 2026 23:56
@don-petry

Copy link
Copy Markdown
Collaborator 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 23:57
@don-petry
don-petry disabled auto-merge June 10, 2026 01:45
@don-petry

Copy link
Copy Markdown
Collaborator 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 01:46
@don-petry
don-petry disabled auto-merge June 10, 2026 01:57
@don-petry

Copy link
Copy Markdown
Collaborator 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 02:00
@don-petry
don-petry disabled auto-merge June 10, 2026 02:08
@don-petry

Copy link
Copy Markdown
Collaborator Author

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

No changes were needed for this PR.

@donpetry-bot
donpetry-bot dismissed their stale review June 10, 2026 02:14

Superseded by automated re-review at b354e28.

@don-petry

Copy link
Copy Markdown
Collaborator Author

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

@don-petry
don-petry disabled auto-merge June 10, 2026 02:20
@don-petry

Copy link
Copy Markdown
Collaborator Author

Auto-rebase failed — merge conflict — this branch has conflicts with main that must be resolved.

Claude will attempt to resolve this automatically. If it cannot, a follow-up comment will explain what needs manual attention.

To resolve manually instead:

git fetch origin
git merge origin/main
# resolve conflicts, then:
git add .
git commit
git push

@don-petry
don-petry dismissed stale reviews from donpetry-bot and coderabbitai[bot] via 3b34ca4 June 10, 2026 02:22
@don-petry
don-petry force-pushed the dev-lead/issue-342-20260609-2108 branch from b354e28 to 3b34ca4 Compare June 10, 2026 02:22
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — rebase (no-changes)

Agent reasoning
PR: #524
Rebased onto: main
Conflicts resolved: 1 file
- .github/workflows/lint.yml: kept PR's change (shellcheck wildcard glob + -x flag)
  over main's explicit file list; a pre-commit hook further improved the command
  to use `find scripts -name "*.sh" -exec shellcheck --severity=warning -x {} +`
Push: success
```
The branch was restructured from 349 entangled commits (full repo history + merge commits) down to 2 clean commits on top of main, then force-pushed successfully.

@don-petry
don-petry enabled auto-merge (squash) June 10, 2026 02:23
@don-petry
don-petry disabled auto-merge June 10, 2026 02:29
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — fix-bot-comment (no-changes)

Agent reasoning
Issues addressed: 0
Files changed: none
Skipped (informational): 0
No actionable findings: SonarCloud Quality Gate passed with 0 new issues and
0 security hotspots. No open review threads from sonarqubecloud[bot] exist.
PR diff contains no SonarQube hotspot patterns. No Tier 1 CI blockers present.
```

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

Copy link
Copy Markdown

@don-petry

Copy link
Copy Markdown
Collaborator 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 02:36

@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: 056156466a3862b3c430fc423698dd16d77b134c
Review mode: triage-approved (single reviewer)

Summary

Broadens the lint workflow's shellcheck job to cover all scripts/**/*.sh and adds -x so source directives resolve cleanly. Targeted fix for issue #342 (Fleet Monitor warning on lint.yml).

Linked issue analysis

Closes #342, a Fleet Monitor health-check tracking a 13.3% failure rate on lint.yml. Replacing the hardcoded 6-script allowlist with a recursive find means newly added shell scripts can't silently bypass shellcheck, which is the right shape of fix for a workflow whose failure mode was missing/changing files. The job still pins --severity=warning (preserving the SC2016 noise-suppression rationale already documented in the inline comment).

Findings

No blocking findings.

  • Coverage now includes scripts/lib/**/*.sh transitively, which is broader than the prior list — desired behavior, and the shellcheck check passed on this commit confirming all scripts currently meet --severity=warning with -x resolution.
  • find ... -exec shellcheck ... {} + groups args into one or more shellcheck invocations; if no .sh files were found, shellcheck would be invoked with zero args and error. Not a concern here (scripts/ is well-populated and the job passed), but worth noting if scripts/ is ever emptied.
  • Inline comment on -x is accurate and helpful for future maintainers.

CI status

All required checks green on 0561564: Lint, ShellCheck, shellcheck (lint), bats, unit-tests, CodeQL (actions/python), Secret scan (gitleaks), Agent Security Scan, AgentShield, validate-agent-profiles, Compile agentic workflows, gh-aw-compile, SonarCloud (Quality Gate passed, 0 new issues), CodeRabbit. Dependency-audit shards skipped (no matching ecosystems). Only review/review still IN_PROGRESS (this run).


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

@don-petry
don-petry merged commit 2a2bce6 into main Jun 10, 2026
27 checks passed
@don-petry
don-petry deleted the dev-lead/issue-342-20260609-2108 branch June 10, 2026 02:40

@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: 056156466a3862b3c430fc423698dd16d77b134c
Review mode: triage-approved (single reviewer)

Summary

Broadens the lint workflow's shellcheck step to cover all scripts/**/*.sh via a find glob (replacing a hand-maintained file list) and adds -x so source directives are followed. CI-only change — no runtime or security impact.

Linked issue analysis

Closes #342, a Fleet Monitor health-check warning about a 13.3% failure rate on lint.yml. The PR broadens shellcheck coverage and follows source directives, which reasonably reduces drift between the hand-maintained list and the actual scripts in the repo. The fleet-tracker issue is informational, so substantive resolution is the workflow hygiene improvement itself.

Findings

No issues.

  • The new find ... -exec shellcheck ... {} + pattern is correct and runs in a single shellcheck invocation per batch.
  • -x is the right way to handle the # shellcheck source= annotations present in the repo's scripts.
  • The shellcheck job passed under the new pattern, confirming all newly-covered scripts still lint clean at warning severity.
  • Severity comment on the previous line remains accurate.

CI status

All required checks green: Lint/shellcheck, Lint/bats, Lint/validate-agent-profiles, Lint/gh-aw-compile, CodeQL (actions + python), CI/ShellCheck, CI/Agent Security Scan, CI/Compile agentic workflows, CI/Secret scan (gitleaks), SonarCloud (quality gate passed, 0 new issues), unit-tests, dependency-audit, AgentShield. Dev-Lead dispatch and this review job are in-flight and don't block.


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

don-petry added a commit that referenced this pull request Jun 12, 2026
…rivate — lint.yml (#524)

* feat: implement issue #342 — [Fleet Monitor] petry-projects/.github-private — lint.yml

* chore: apply manual instructions [skip ci-relay]

---------

Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Jun 14, 2026
…rivate — lint.yml (#524)

* feat: implement issue #342 — [Fleet Monitor] petry-projects/.github-private — lint.yml

* chore: apply manual instructions [skip ci-relay]

---------

Co-authored-by: donpetry-bot <281750570+donpetry-bot@users.noreply.github.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-private — lint.yml

3 participants