@kapa.ai can you help me merge through the PRs associated with these issues? https://github.com/airbytehq/airbyte/issues/80160 https://github.com/airbytehq/airbyte/issues/80211 https://github.com/airbytehq/airbyte/issues/80250

There’s only partial information in the provided knowledge sources about those specific issues and their PRs, so I can’t see the full current status or directly help “push them through.” I can, however, point you to the documented process and what you can do to move them forward. From the context: • Issue #80160 is referenced by PR #80161, which optimizes

_id

type discovery in

source-mongodb-v2

by adding a

$sample

stage to avoid full collection scans. [MongoDB v2 PR] • Issue #80211 and #80250 are not detailed in the supplied documents, so I don’t have visibility into their associated PRs or current review state. Given that limitation, here’s what you can do to help get these PRs merged, based on Airbyte’s contribution and support docs: 1. Ensure each PR is correctly set up ◦ Each PR should: ▪︎ Be linked to its corresponding GitHub issue (not labeled

needs triage

). [Contributing – code; Contributing forum answer] ▪︎ Have a clear title and description following the Pull Request Handbook and template. [Contributing – code; Contributing forum answer] ▪︎ Limit scope to a single connector per PR. [Get support – contributions] 1. Check contribution type is acceptable ◦ Airbyte currently: ▪︎ Accepts source connector contributions (fixes/enhancements, new streams, new API sources, migrations to Connector Builder). ▪︎ Does not accept platform contributions or destination connector contributions. [Contributing – code] ◦ Make sure your PRs fall into the accepted categories; otherwise they may not be merged. 1. Verify CLA and PR permissions ◦ Ensure you’ve signed the *CLA*; PRs without it or without updates can be closed for inactivity. [Contributing forum answer] ◦ Make sure “Allow edits from maintainers” is enabled so maintainers can push fixes to your branch. [PR fork permission warning] 1. Wait for maintainer review and respond quickly ◦ An Airbyte maintainer must trigger CI and review the code; they’ll leave feedback you should address promptly. [Contributing – code; Contributing forum answer] ◦ Submitting a PR doesn’t guarantee merge; it’s evaluated for quality and alignment with project goals. [Get support – contributions] 1. Track status and ask for updates in the right places ◦ Check the Community Pull Requests project board to see where your PRs sit in the review pipeline. [Get support – contributions] ◦ For status nudges, you can: ▪︎ Comment on the PRs (e.g., summarizing impact, confirming tests, answering any open questions). ▪︎ Ask in the Airbyte Community Slack (link from the docs) and reference the issue/PR numbers. [Get support – contributions] Because I don’t have the full content of issues #80211 and #80250 or their PRs in the knowledge sources, I can’t give PR-specific guidance beyond this general process. If you share the PR links themselves or their current blockers (e.g., failing checks, requested changes), I can help you interpret those based on the docs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.