Given the webhook-support findings (#2), how does the cache actually get refreshed: which sources use a webhook push (and what receives it — a Symfony endpoint per account/subscription?), which fall back to polling, and for polling, what triggers it — Symfony Scheduler, a bin/console command on cron, or lazy on-request refresh when last_synced_at is stale? Zoom into the entity schema ticket (#4) as needed for column names.
Part of #1
Blocked by: #2
## Question
Given the webhook-support findings (#2), how does the cache actually get refreshed: which sources use a webhook push (and what receives it — a Symfony endpoint per account/subscription?), which fall back to polling, and for polling, what triggers it — Symfony Scheduler, a bin/console command on cron, or lazy on-request refresh when last_synced_at is stale? Zoom into the entity schema ticket (#4) as needed for column names.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #1
Blocked by: #2
Question
Given the webhook-support findings (#2), how does the cache actually get refreshed: which sources use a webhook push (and what receives it — a Symfony endpoint per account/subscription?), which fall back to polling, and for polling, what triggers it — Symfony Scheduler, a bin/console command on cron, or lazy on-request refresh when last_synced_at is stale? Zoom into the entity schema ticket (#4) as needed for column names.