From 8c903c9449d387c9b0edefa5aa283b176a3ed0cb Mon Sep 17 00:00:00 2001 From: DanConwayDev Date: Fri, 13 Feb 2026 17:42:08 +0000 Subject: fix: revert wrong sync approach for purgatory announcements The partial fix treating ProcessResult::Purgatory as confirmed in pending_sync_index would trigger full L2/L3 sync for purgatory announcements. Per design (decision #6), purgatory announcements should only sync state events via SyncLevel::StateOnly (not yet implemented). Ignore test_archive_read_only_creates_bare_repo until SyncLevel is implemented in Phase 3. --- src/purgatory/sync/context.rs | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) (limited to 'src/purgatory/sync/context.rs') diff --git a/src/purgatory/sync/context.rs b/src/purgatory/sync/context.rs index 778cdb8..33c2d12 100644 --- a/src/purgatory/sync/context.rs +++ b/src/purgatory/sync/context.rs @@ -279,12 +279,7 @@ impl SyncContext for RealSyncContext { } async fn fetch_repository_data(&self, identifier: &str) -> Result { - crate::git::authorization::fetch_repository_data_with_purgatory( - &self.database, - &self.purgatory, - identifier, - ) - .await + crate::git::authorization::fetch_repository_data(&self.database, identifier).await } fn collect_needed_oids(&self, identifier: &str) -> HashSet { -- cgit v1.2.3