Based on the knowledge sources, here are the typical next steps for your PR: 1. Ensure PR requirements are met: ◦ Your PR is linked to an existing GitHub issue (without the

needs triage

label) ◦ The PR title and description follow the Pull Request Handbook ◦ "Allow edits from maintainers" is enabled and the PR is from a personal fork (not an organization fork) [PR Permissions] 1. Wait for a maintainer to trigger CI tests. An Airbyte maintainer will kick off the CI tests and begin a code review. [Code Contributions] 2. Respond to feedback. Review and respond to any questions or requested changes from Airbyte maintainers promptly — PRs with no updates may be closed due to inactivity. [Forum Post] 3. Track your PR status. Check the Community Pull Requests board to see where your PR stands in the review queue. [Getting Support] 4. Reach out on Slack if you need a status update via the #C027KKE4BCZ channel. > Note: I don't have direct visibility into the current state of your specific PR, so I'd recommend checking the PR comments and the Community Pull Requests board for the most accurate status. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.