[don-petry]

Follow-up to the org rename: moves this repo's SonarCloud config from the petry-projects SonarCloud organization to the new combsmith one (piloted on combsmith/markets#530: analysis succeeded with the existing SONAR_TOKEN once Automatic Analysis was off).

2 files changed, 13 insertions(+), 13 deletions(-)

🤖 Generated with Claude Code

Problem

See the linked issue.

Risk

Low — changes automation shell logic under scripts/, covered by shellcheck (--severity=warning) and the bats suite.

Test plan

Tests added/updated: tests/scripts/sonar-config.test.sh. Verification: bash scripts/dev-lead-lint.sh (shellcheck --severity=warning) ran pre-commit; the bats suite runs in CI.

Rollback

Revert this PR. No non-revertible side effects (no tags, migrations, or external state).

Monitoring

This PR's Lint (shellcheck) and bats checks show pass/fail; watch subsequent dev-lead / pr-review runs for behavioral regressions.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-14T21:23:45.361527Z	415efd4	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

Warning

.coderabbit.yaml has a parsing error

The CodeRabbit configuration file in this repository has a parsing error and default settings were used instead. Please fix the error(s) in the configuration file. You can initialize chat with CodeRabbit to get help with the configuration file.

Parsing errors: 1

Validation error: Invalid input: expected string, received object at "reviews.path_filters[3]"

⚙️ Configuration instructions

• Please see the configuration documentation for more information.
• You can also validate your configuration using the online YAML validator.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: af68ee3a-e59c-4e37-a598-3100dafa27b5

📥 Commits

Reviewing files that changed from the base of the PR and between 5c86c3a and 415efd4.

📒 Files selected for processing: 2

• sonar-project.properties
• tests/scripts/sonar-config.test.sh

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated the code-quality analysis project and organization identifiers so future reports are associated with the new project.
  • Updated related test examples and fixtures to reflect the new identifiers; test logic is unchanged.
  • No end-user features or interface changes are included.

The SonarQube project key and organization changed to combsmith_broodly and combsmith. The test example and fixtures now use the updated project key.

Changes: SonarQube Project Identity

Layer / File(s)	Summary
Update SonarQube project identity sonar-project.properties, tests/scripts/sonar-config.test.sh	The project key and organization changed in the SonarQube configuration. The test example and fixtures now use combsmith_broodly.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 415ef

No actionable issue is established by the reviewed changes. The SonarCloud scan will confirm access to the renamed project.

Pre-merge checks: 5

Passed checks: 5 passed

Check name	Status	Explanation
Docstring Coverage		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 1…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Title check		The title clearly identifies the primary change: updating SonarCloud reporting to the combsmith organization.
Description check		The description directly explains the SonarCloud organization rename, affected configuration, testing, risk, and rollback plan.

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

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.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[don-petry]

dependency-audit / govulncheck verifies that the Go modules have no known reachable vulnerabilities. It did not reach that verdict here: govulncheck@v1.1.4 panics (unexpected expr: *ast.KeyValueExpr) while analysing ./apps/api on the runner's Go 1.27.2, so the tool crashed before producing any findings. This PR only touches sonar-project.properties and tests/scripts/sonar-config.test.sh, so it cannot cause the crash. I made no change, because the audit workflow is a synced org-standard stub and the fix is a govulncheck version bump upstream in combsmith/.github. Rerun the check once that lands.

[don-petry]

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

PR: #602
No changes were committed, but the PR still can't be marked done: required checks Go, SonarCloud, TypeScript, agent-shield / AgentShield are still pending. The retry cron will re-attempt automatically. Next attempt after: 2026-10-14T21:54:44Z

[don-petry]

Note

@don-petry I reviewed this PR and no code changes were needed, but I can't mark it done yet: required checks Go, SonarCloud, TypeScript, agent-shield / AgentShield are still pending. I'll re-check automatically.
Next attempt after: 2026-10-14T21:54:44Z

[don-petry]

Dev-Lead — waiting on PR blockers (intent: fix-reviews)

PR: #602
No changes were committed, but the PR still can't be marked done: required checks Go, TypeScript are still pending. The retry cron will re-attempt automatically. Next attempt after: 2026-10-14T21:57:16Z