NAME

repomatic unsubscribe-threads - Unsubscribe from closed, inactive notification threads

SYNOPSIS

repomatic unsubscribe-threads [OPTIONS]

DESCRIPTION

Unsubscribe from closed, inactive GitHub notification threads.

Processes notifications in two phases:

Phase 1, REST notification threads:


  Fetches Issue/PullRequest notification threads, inspects each for


  closed + stale status, and unsubscribes via DELETE + PATCH.

Phase 2, GraphQL threadless subscriptions:


  Searches for closed issues/PRs the user is involved in and


  unsubscribes via the updateSubscription mutation.

OPTIONS

--months INTEGER RANGE: Inactivity threshold in months. Threads updated more recently are kept.
--max-unsubscribes INTEGER RANGE: Maximum unsubscribes per phase. Inspection is not capped.
--dry-run / --live: Report what would be done without making changes.
--help / -h: Show this message and exit.

ENVIRONMENT

UNSUBSCRIBE_THREADS_MONTHS: Inactivity threshold in months. Threads updated more recently are kept.
UNSUBSCRIBE_THREADS_MAX_UNSUBSCRIBES: Maximum unsubscribes per phase. Inspection is not capped.
UNSUBSCRIBE_THREADS_DRY_RUN: Report what would be done without making changes.
UNSUBSCRIBE_THREADS__CLICK_DEFAULT_HELP: Show this message and exit.

EXIT STATUS

0: Success.
1: A runtime error, or an aborted prompt (Ctrl-C, a declined confirmation).
2: A usage error: unknown option, invalid value, missing operand, or an unparsable configuration file.

EXAMPLES

Dry run to preview what would be unsubscribed

repomatic unsubscribe\-threads \-\-dry\-run

Unsubscribe from threads inactive for 6+ months

repomatic unsubscribe\-threads \-\-months 6

Unsubscribe from at most 50 threads per phase

repomatic unsubscribe\-threads \-\-max\-unsubscribes 50

AUTHORS

Kevin Deldycke