arr/blocklists
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Document manual blacklist additions in README

Browse Source 
Add a "Maintaining the blacklist" section that mirrors "Maintaining
the whitelist" and explains the manual-addition escape hatch
preserved by the three-way merge. Clarify that direct removals do
not work and must go through the whitelist instead.
This commit is contained in:
CodeX
2026-04-07 01:26:13 +02:00
parent 570fa858e8
commit 2f2ac6897f
1 changed files with 16 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+16
View File
@@ -99,6 +99,22 @@ with exact-string set subtraction:
See [Lists](https://git.hisp.no/arr/blocklists/wiki/Lists) for the full See [Lists](https://git.hisp.no/arr/blocklists/wiki/Lists) for the full
pattern rules and examples. pattern rules and examples.
## Maintaining the blacklist
Most blacklist maintenance happens through the whitelist (above). To **add**
an entry that upstream Cleanuparr does not block -- a tracker-specific junk
file, a new malware extension, anything else upstream missed -- edit
`blacklist` directly in Gitea, add the line, commit. The next sync run
detects the new line as a manual local addition and preserves it across
every subsequent sync.
To **remove** an entry, use `whitelist` instead. Deleting a line from
`blacklist` does not work as a removal mechanism: the next sync re-adds it
from upstream. Removals must go through the whitelist.
See [Lists](https://git.hisp.no/arr/blocklists/wiki/Lists) for the full
rules and worked examples.
## Sync schedule ## Sync schedule
The Gitea Actions workflow runs every 7 days at 04:00 UTC and on manual The Gitea Actions workflow runs every 7 days at 04:00 UTC and on manual