dheerajturaga opened a new pull request, #75336: URL: https://github.com/apache/airflow/pull/75336
Part of [AIP-125 (Inbound Webhooks)](https://lists.apache.org/thread/p3dpnor4zwko8tldpncj6ftj1bpp18q7), which lets external services such as GitHub trigger Dags by sending webhooks to Airflow. This is part of Phase 2 (webhook waits and asset routes), which targets Airflow 3.5. As a GitHub provider change, it ships in a GitHub provider release rather than with Airflow. The `github` source type now sets the correlation key `<repository>#<number>`, such as `my-org/web#7`, on every delivery about a pull request or an issue. GitHub is the reference source for webhook waits, and a delivery that arrives before the wait it is meant for is kept for that wait only when it has a correlation key ({{PR-27}}). Deliveries can already be filtered by the key in the UI and the REST API, and topic events already carry it as `correlation_key` in their extra, which was null for GitHub until now. - The key includes the repository because a plain number collides across the repositories of an organization webhook. - Pull requests and issues share one sequence of numbers per repository, so a review or a comment on pull request 7 carries the pull request's key. A `push`, a `workflow_run` or an organization event has no key, and a renamed or transferred repository gets new keys. - Core answers a key longer than 255 characters with a 500, so a delivery that would produce one goes without a key. Real GitHub keys are far shorter. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5.5) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) --- * Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)** for more information. Note: commit author/co-author name and email in commits become permanently public when merged. * For fundamental code changes, an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals)) is needed. * When adding dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). * For significant user-facing changes create newsfragment: `{pr_number}.significant.rst`, in [airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments). You can add this file in a follow-up commit after the PR is created so you know the PR number. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
