SCANPY-251 Move ownership to CI Experience squad

[Seppli11]

---

Summary by Gitar

• Codeowners update:
  • Changed ownership of .github/CODEOWNERS from @SonarSource/quality-data-ml-squad to @SonarSource/code-quality-ci-experience-squad.
• GHA Migration:
  • Migrated SlackNotify.yml to use workflow_run triggers and updated the Slack channel to ops-ci-experience.
  • Updated MacOsNightly.yml to route Slack notifications to ops-ci-experience and corrected the actions/checkout commit hash.

_{This will update automatically on new commits.}

[hashicorp-vault-sonar-prod]

SCANPY-251

[guillaume-dequenne]

LGTM

[sonarqube-next]

Quality Gate passed for 'Python Scanner'

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[gitar-bot]

Code Review ✅ Approved 2 resolved / 2 findings

Updates CODEOWNERS to reflect the shift to the CI Experience squad and migrates Slack notifications to the appropriate ops channel, resolving issues with duplicate alerts and branch filtering.

✅ 2 resolved

✅ Quality: Duplicate Slack alerts for macOS Nightly Build failures

📄 .github/workflows/SlackNotify.yml:4-18 📄 .github/workflows/MacOsNightly.yml:109-119
SlackNotify.yml now triggers on workflow_run completion (conclusion == failure) for the workflow named "macOS Nightly Build". However, MacOsNightly.yml still contains its own "Send Slack notification" step (lines 109-119) that fires to the same ops-ci-experience channel on failure. As a result, a failed macOS nightly run will send two near-identical Slack messages: one from the workflow's internal step and one from the centralized SlackNotify workflow. Consider removing the inline notification step from MacOsNightly.yml (and any other listed workflow with its own failure notifier) now that SlackNotify centralizes failure alerts, or excluding it from SlackNotify's workflow_run list.

✅ Edge Case: sonar-release failures may not match the branches filter

📄 .github/workflows/SlackNotify.yml:4-17
The workflow_run trigger restricts notifications to branches main, master, branch-*, and dogfood-*. The sonar-release workflow is triggered when publishing a GitHub release, so its head_branch is typically the release tag rather than one of these branch names. If the release run's head branch does not match the filter, SlackNotify will silently skip notifying on a failed release — arguably the most important case to alert on. Verify that github.event.workflow_run.head_branch for release runs matches the configured branch patterns, or relax/adjust the filter for the release workflow.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}