Apply account repository policy

[crmne]

Align this repository with the account-wide maintainer, review, release-notes, triage, board, sponsorship, and dependency policy.

Summary by CodeRabbit

• Reliability
  • Issue assessments now keep queued runs when a bot-comment run is skipped. This helps ensure pending assessments are not displaced by skipped runs, while preserving the existing concurrency behavior for runs that do proceed.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 7df16236-0d65-4101-8725-56e975788b57

📥 Commits

Reviewing files that changed from the base of the PR and between e17d9f3 and b80e724.

📒 Files selected for processing (1)

• .github/workflows/issue-assessment.yml

Limit details: You’ve used all 10 included reviews currently available.

---

📝 Walkthrough

Walkthrough

Concurrency control moved from workflow scope to the assess job. The concurrency group expression and cancel-in-progress: false setting remain unchanged. A comment describes how skipped bot-comment runs relate to queued runs.

Changes

Issue assessment workflow

Layer / File(s)	Summary
Assess job concurrency .github/workflows/issue-assessment.yml	The concurrency group and cancel-in-progress: false setting move to the assess job. A comment describes the handling of skipped bot-comment runs.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to b80e7

Eligible issue assessments retain their serialization, and no concrete disruption is established. Whether skipped runs can affect pending assessments remains unconfirmed.

Architecture Summary

Architecture risk: 🔵 Low · up to b80e7

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .github/workflows/issue-assessment.yml: The concurrency group and cancel-in-progress: false setting were removed from workflow scope and added to the assess job, retaining the same group expression. A comment was added describing the intended handling of skipped bot-comment runs.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title matches the stated objective to apply the account repository policy. It is broader than the specific concurrency change, but it remains related to the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

Usage-based review receipt

• Mode: Continue automatically
• Reviewed files: 1
• Waived: $0.25 (charged $0.00)
• View usage details

Note

This review exceeded your plan’s limits and used usage-based reviews—free during trial, billed after paid activation unless disabled. Manage usage-based reviews.

---

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