From 8ae8a48457dac8397e94f7db44711c1517fd2ea0 Mon Sep 17 00:00:00 2001 From: Chris Caron Date: Tue, 19 Apr 2022 13:14:00 -0400 Subject: [PATCH] Updated config (markdown) --- config.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.md b/config.md index 758b8ac..e84cc17 100644 --- a/config.md +++ b/config.md @@ -149,7 +149,7 @@ apprise -b "has (TagA AND TagB) OR TagC" --tag="TagA, TagB" --tag=TagC The following special tags are reserved for use | Tag | Usage | Description | | --------------- | -------- |------------- | -| `always` | config | If you store an Apprise entry in a config file and associate the `always` tag with it, it will **ALWAYS** be notified reguardless of any tagging restriction you place on the CLI +| `always` | config | If you store an Apprise entry in a config file and associate the `always` tag with it, it will **ALWAYS** be notified regardless of any tagging restriction you place on the CLI | `all` | notifications | When performing a notification, you always have the ability to filter which services are notified based on the tags you've assigned them. However if you perform a notification and indicate that you want to notify and are filtering on the `all` tag, absolutely everything will be notified (regardless of what other tags have been assigned to it). It's also worth noting that if you do not assign a tag to an Apprise configuration entry, it can only be actioned/notified if the call to Apprise also does not identify a tag to filter on. However un-tagged configuration entries will be always included in `all` references.