ci(hydra-automerge): tag owning team in auto-merge Slack notification

[devin-ai-integration]

Opened at Jim Ruppert's request; feature originally requested by Patrick Nilan in the #hydra-feedback Slack channel.

What

Requested by Patrick Nilan in #hydra-feedback, with scope confirmed by Jim Ruppert: today's :robot_face: Hydra Auto-Merge Slack post to #hydra-hands-free notifies nobody, so the team that owns the auto-merged connector code has no visibility and no prompt to confirm whether the merge was correct or erroneous.

This tags the owning oncall group in that existing notification.

How

New Resolve owning team mentions for Slack step (same guard conditions as the Slack post, running in the already-checked-out PR head tree) derives the modified connectors from the PR file list and maps them to a group:

destination-*                                 -> @oc-db-dw (S0BKLTJNKC6)
source-* with language:java|kotlin            -> @oc-db-dw
source-* otherwise (manifest/low-code/python) -> @oc-apis  (S08SNSK5RHQ)

Language comes from metadata.yaml tags, matching the identify-oncall-contact skill's classification rule. Connector names are also recovered from docs/integrations/{sources,destinations}/<name>.md paths so docs-only auto-merges still route. A mixed PR tags both groups; mentions render as <!subteam^ID|@alias> in the message body so Slack actually notifies the group.

Review guide

1. .github/workflows/hydra-automerge.yml — the new step and the added mention line in the Slack section block.

User Impact

Auto-merged connector PRs now ping @oc-apis or @oc-db-dw in #hydra-hands-free with a request to review the merge. No change to auto-merge eligibility, gating, or merge behavior. Destination changes remain deterministically ineligible for auto-merge, so the @oc-db-dw path fires today only for Java/Kotlin sources.

Can this PR be safely reverted and rolled back?

• YES 💚

---

Devin session

[github-actions]

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

• 🛠️ Quick Fixes
  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions, scraping changelog description from the PR title.
    • Bump types: patch (default), minor, major, major_rc, rc, promote.
    • The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
    • The promote type strips the RC suffix to finalize a release.
    • Example: /bump-version type=rc or /bump-version type=minor
  • /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
• ❇️ AI Testing and Review (internal link: AI-SDLC Docs):
  • /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
  • /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
• 📝 AI Documentation:
  • /ai-docs-review - AI-powered documentation review for PRs with connector changes.
  • /ai-create-docs-pr - Creates a documentation PR for connector changes, stacked on the current PR.
• 🚀 Connector Releases:
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • /enable-autopilot-rollouts - Enables autopilot progressive rollouts for the modified connector(s) in the PR, remediating "autopilot rollouts not enabled for {connector-name}" auto-merge blockers. Sets defaultRolloutMode: autopilot and enableProgressiveRollout: true, preserving any existing autopilotConfig.
    • Optional args: connector=<CONNECTOR_NAME> (defaults to the modified connectors in the PR), strategy=fast|slow|default (defaults to fast).
    • Example: /enable-autopilot-rollouts or /enable-autopilot-rollouts connector=source-faker strategy=slow
• ☕️ JVM connectors:
  • /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
    Example: /update-connector-cdk-version connector=destination-bigquery
• 🐍 Python connectors:
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
• ⚙️ Admin commands:
  • /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
    Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

• Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
• Developing Connectors Locally
• Managing Connector Secrets
• On-Demand Regression Tests
• #connector-ci-issues
• #connector-publish-updates
• #connector-build-statuses

📝 Edit this welcome message.