Previously, all incoming GitHub webhook events were processed sequentially without repository-level parallelism, which could lead to bottlenecks on high-activity days. By adding an org/repo-based concurrency key to the event processing task, events across different repositories can now be processed in parallel. This improves overall throughput while ensuring events within the same repository are still handled in an orderly fashion.