Mark a repository as ignored so a known-bad repo stops failing every sync #119

Open
opened 2026-10-11 12:19:32 +00:00 by KofTwentyTwo · 1 comment
KofTwentyTwo commented 2026-10-11 12:19:32 +00:00 (Migrated from github.com)

A repository in the list can be marked 'ignored' (per account): it is skipped by Sync and Sync All, shown with an Ignored state and excluded from the Failed count, and can be un-ignored later. Use case: a repository that cannot be cloned on Windows (invalid paths) or that the user does not care about for now should not turn every sync red. Persisted with the account (not the vault). Requested by the owner on 2026-10-11. Feature request only; not scheduled.

A repository in the list can be marked 'ignored' (per account): it is skipped by Sync and Sync All, shown with an Ignored state and excluded from the Failed count, and can be un-ignored later. Use case: a repository that cannot be cloned on Windows (invalid paths) or that the user does not care about for now should not turn every sync red. Persisted with the account (not the vault). Requested by the owner on 2026-10-11. Feature request only; not scheduled.
KofTwentyTwo commented 2026-10-11 12:28:58 +00:00 (Migrated from github.com)
Discussed in https://github.com/KofTwentyTwo/gclo/discussions/125 (Ideas).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: KofTwentyTwo/gclo#119