diff options
| author | DanConwayDev <DanConwayDev@protonmail.com> | 2026-02-17 11:43:40 +0000 |
|---|---|---|
| committer | DanConwayDev <DanConwayDev@protonmail.com> | 2026-02-17 11:43:40 +0000 |
| commit | cad58fccae7ed84bb033e56de0f1323b714a854d (patch) | |
| tree | 9635381a3a8c35d8e4f83f2686304874b1523433 /docs | |
| parent | efbbcc49ae8e8f598a24c939b35ad9cda0541663 (diff) | |
docs: clarify why fetch_repository_data excludes purgatory
Add comments explaining that PR event processing (both incoming and
purgatory) should only use database announcements, not purgatory ones.
This is intentional because:
- Incoming PR events should only be accepted for validated announcements
- Purgatory PR events should only be released when announcement is promoted
- This prevents accepting PR events for announcements that fail validation
Differs from state event processing which uses fetch_repository_data_with_purgatory
because state events check authorization without releasing from purgatory.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions