[Docs]: PR titles

[carloseguevara]

Page URL

https://docs.airbyte.com/community/contributing-to-airbyte/resources/pull-requests-handbook

Description

The pull requests handbook is not aling with the CI validation. In the CI check the title must follow the conventional commits structure, but in the handbook different examples are showed.

---

Internal Tracking: https://github.com/airbytehq/oncall/issues/11835

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will do an initial review and may:

• Ask clarifying questions if needed
• Suggest relevant documentation or workarounds
• Flag this for internal visibility

Note: Community issues are reviewed on a best-effort basis and do not have a guaranteed response time. For additional help:

• Join the Airbyte Community Slack to connect with other users and community members
• If you're an Airbyte Cloud customer, you can open a support ticket or contact your account representative, referencing this issue URL

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/cb81e948e1f3485694a484a75e5fb607

✅ Devin AI session created successfully!

[devin-ai-integration]

Hi Carlos Eduardo Guevara Parrales (@carloseguevara), thank you for reporting this issue!

You are correct — the Pull Requests Handbook currently shows emoji-based PR title conventions (e.g., ✨ Source E-Commerce: add new stream), but the CI check enforces the Conventional Commits format (e.g., feat(connectors): add new stream). This misalignment can be confusing for contributors.

I have flagged this for the internal documentation team to update the handbook so it aligns with the actual CI validation rules.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

[devin-ai-integration]

This issue has been escalated to the internal team for resolution: https://github.com/airbytehq/oncall/issues/11835

[amarishalvorsen-debug]

Hi, Thanks for flagging this. The mismatch between the handbook and CI requirements is confusing—agree it should be aligned. Let me know if there’s a preferred format we should follow in the meantime. Thanks

…

On Tue, Mar 31, 2026, 6:38 PM devin-ai-integration[bot] < ***@***.***> wrote: *devin-ai-integration[bot]* left a comment (airbytehq/airbyte#75951) <#75951 (comment)> This issue has been escalated to the internal team for resolution: airbytehq/oncall#11835 <https://github.com/airbytehq/oncall/issues/11835> — Reply to this email directly, view it on GitHub <#75951?email_source=notifications&email_token=CAF2FZETPRVYFQURJ4U3T7L4TRJGJA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJWGYZTONBQGE32M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4166374017>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CAF2FZCOD4Q7ODFLKGQHRTT4TRJGJAVCNFSM6AAAAACXINX4O6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNRWGM3TIMBRG4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>