Henry Bogardus
06/22/2026, 9:10 PMkapa.ai
06/22/2026, 9:10 PMauto-merge label applied, GitHub's native auto-merge will wait for required CI checks to pass and then automatically squash-merge the PR. [auto-merge refactor]
2. Force-Merge (Bypass CI Checks) If you need to bypass CI checks, you can use the /force-merge slash command by commenting on the PR:
/force-merge reason="<YOUR_REASON>"
This requires a reason to be provided. [internal PR guide]
3. AI-Gated Auto-Merge (/ai-ready) For connector PRs that have passed AI review, you can trigger the Hydra AI-gated auto-merge workflow:
/ai-ready
Or for a dry run (evaluate without merging):
/ai-ready dry-run=true
This evaluates gates like no breaking changes, AI review passed, and change scope (docs-only, dependency bump, metadata-only, etc.) before merging. [Hydra AI workflow]
Notes ⢠The /force-merge command requires Airbyte Maintainer privileges to execute. If you're a community contributor, you'll need to ask a maintainer to run it for you. [community PR guide]
⢠For community contributions, the standard path is to wait for a maintainer review and approval, after which the PR can be merged normally. [contributing guide]
Could you share more details about your specific situation (e.g., are you an Airbyte team member or community contributor, and what's blocking the merge)? That would help narrow down the best approach. š 0 button š 0 button ā¹ļø Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.Henry Bogardus
06/23/2026, 5:56 PM