Rephrase documentation and link to docs on exit codes feature (#798).

borgmatic-collective · Jan 21, 2024 · f9998b5 · f9998b5
1 parent 5f921a7
commit f9998b5
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 3 deletions.
diff --git a/NEWS b/NEWS
@@ -1,7 +1,9 @@
 1.8.7
  * #736: Store included configuration files within each backup archive in support of the "config
    bootstrap" action. Previously, only top-level configuration files were stored.
- * #798: Elevate specific Borg warnings to errors or squash errors to warnings.
+ * #798: Elevate specific Borg warnings to errors or squash errors to
+ * warnings. See the documentation for more information:
+   https://torsion.org/borgmatic/docs/how-to/customize-warnings-and-errors/
  * #810: SECURITY: Prevent shell injection attacks within the PostgreSQL hook, the MongoDB hook, the
    SQLite hook, the "borgmatic borg" action, and command hook variable/constant interpolation.
  * #814: Fix a traceback when providing an invalid "--override" value for a list option.

diff --git a/docs/how-to/customize-warnings-and-errors.md b/docs/how-to/customize-warnings-and-errors.md
@@ -82,5 +82,5 @@ a backup file is not found:
 terminating with warning status, rc 107
 ```
 
-The exit status to use in that case would be `107` if you want to configure
-borgmatic to treat it as an error.
+So if you want to configure borgmatic to treat this as an error instead of a
+warning, the exit status to use is `107`.