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.
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.
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.
Discussed in https://github.com/KofTwentyTwo/gclo/discussions/125 (Ideas).