feat(project-meta-sync): add aging and SLA annotations

[ashleyshaw]

Summary

• enhance project-meta-sync.yml to annotate issue/PR aging and SLA state
• keep existing label/state -> project field mapping behaviour intact
• avoid annotation spam by upserting a single marker-based comment per item

Changes

• Updated .github/workflows/project-meta-sync.yml
  • workflow permissions elevated to allow issue/PR comments (issues:write, pull-requests:write)
  • added SLA thresholds in env:
    • SLA_WARN_DAYS=7
    • SLA_BREACH_DAYS=14
  • added Add or update aging and SLA annotation step using actions/github-script
    • computes item age in days
    • sets SLA state (Within SLA, SLA risk, SLA breached)
    • upserts comment via marker <!-- project-meta-sync:sla -->

Acceptance criteria mapping (#65)

• maps labels/state -> project custom fields: already present and preserved
• adds aging/SLA annotations: implemented as issue/PR comments
• automation tested: workflow validation and lint run locally
• docs/changelog: no user-facing docs required; internal workflow behaviour only

Validation

• npx spectral lint .github/workflows/project-meta-sync.yml --ruleset .spectral-workflows.cjs
• node scripts/validation/validate-workflows.js

Link

• Closes [Workflows] Project meta sync + aging/SLA annotations #65

[gemini-code-assist]

Note

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

[coderabbitai]

Warning

Review limit reached

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

More reviews will be available in 11 minutes and 39 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: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 88dbd1e8-0be6-486a-9b69-a6b6a5d388d5

📥 Commits

Reviewing files that changed from the base of the PR and between f19ddb1 and e746abc.

📒 Files selected for processing (1)

• .github/workflows/project-meta-sync.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/65-project-meta-sla

---

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 and usage tips.}

[github-actions]

🔍 Reviewer Summary for PR #453

CI Status: ✅ success
Files changed: 1

Recommendations

• Ready to proceed pending human review

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e746abc8aa

ℹ️ 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]

Paginate before creating SLA comments

For issues or PRs that already have more than 100 comments before this annotation is first added, this only inspects the first page of comments. Because GitHub issue comments are returned oldest-first by default and per_page is capped at 100, the newly-created marker can sit after page 1; subsequent edited, labeled, or synchronize events will not find it and will create another SLA comment each time, defeating the single marker-based upsert.

Useful? React with 👍 / 👎.