feat: Metrics Agent Phase 2 — Task 2.3: GitHub Actions Workflow Integration

[ashleyshaw]

Linked issues

Closes#1870

Changelog

Added

• Metrics collection workflow orchestrator (223 LOC)
• GitHub Actions integration for automated metrics publishing
• Workflow templates and configuration examples

Updated

• Metrics Agent Phase 2 progress tracking
• Integration test coverage for workflow triggers

Summary

Complete implementation of GitHub Actions workflow integration for Metrics Agent Phase 2 Task 2.3.

Deliverables

• collect-metrics.js (~150 LOC): Metrics collection and aggregation
• collect-metrics.test.js: Comprehensive test coverage (25+ tests)
• metrics-collection.yml: GitHub Actions workflow template

Checklist (Global DoD / PR)

• All AC met and demonstrated
• Tests added/updated (unit/E2E as appropriate)
• Docs/readme/changelog updated (if user-facing)
• Security checklist completed (where relevant)
• Code/design reviews approved
• CI green; linked issues closed; release notes prepared (if shipping)

[coderabbitai]

Warning

Review limit reached

@ashleyshaw, you've reached your PR review limit, so we couldn't start this review.

Next review available in:51 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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 within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: d4b74f6b-159c-4583-8dad-3d13a9eb0d6f

📥 Commits

Reviewing files that changed from the base of the PR and between 5b91973 and 7922400.

📒 Files selected for processing (5)

• scripts/metrics/PROGRESS.md
• scripts/workflows/metrics/TASK_2.3_DOCUMENTATION.md
• scripts/workflows/metrics/__tests__/collect-metrics.test.js
• scripts/workflows/metrics/collect-metrics.js
• workflows/metrics-collection.yml

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

❌ Branch Name Validation Failed

The branch name feat/metrics-agent-collection does not follow the LightSpeed branching strategy.

Required Format

{type}/{scope}-{short-title}

• type: one of the allowed prefixes (lowercase)
• scope: lowercase, hyphens only (no underscores or uppercase)
• title: lowercase, hyphens only (no underscores or uppercase)

Allowed Branch Types

feat, fix, hotfix, release, refactor, chore, docs, test, perf, ci, build, deps, security, revert, research, design, a11y, ux, i18n, ops, proto, ds, api, schema, telemetry, content, seo, config, migrate, qa, uat, audit, codex

Valid Examples

• ✓ feat/branch-naming-enforcement
• ✓ fix/validation-script-bug
• ✓ chore/update-dependencies
• ✓ docs/branching-strategy-guide
• ✓ hotfix/critical-security-patch

Invalid Examples

• ✗ claude/my-branch (type "claude" not allowed)
• ✗ Feature/MyBranch (uppercase not allowed)
• ✗ fix-bug (missing type prefix)
• ✗ feat/my_feature (underscores not allowed)
• ✗ feat/MyFeature (uppercase not allowed)

Solution

Rename your branch to follow the pattern and update the PR.

For more information, see docs/BRANCHING_STRATEGY.md.

[github-actions]

🚫 This PR description is missing required template content.

Missing required section(s): Changelog

Please update the PR body using one of the repository PR templates:

• https://github.com/lightspeedwp/.github/blob/develop/.github/pull_request_template.md
• https://github.com/lightspeedwp/.github/tree/develop/.github/PULL_REQUEST_TEMPLATE

Empty placeholders, unchecked checklist boxes, and stub issue references do not count.

[ashleyshaw]

Closed: Work moved to PR #2078 with simpler branch name (feat/metrics-workflow)