From fd485e64a399560d8446bc11d7384813ece2af7a Mon Sep 17 00:00:00 2001 From: Dan Helfman Date: Fri, 30 Jan 2026 22:43:54 -0800 Subject: [PATCH] Fix incorrect deprecated hook option name in documentation. --- .../backup-to-a-removable-drive-or-an-intermittent-server.md | 2 +- docs/reference/configuration/command-hooks.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/how-to/backup-to-a-removable-drive-or-an-intermittent-server.md b/docs/how-to/backup-to-a-removable-drive-or-an-intermittent-server.md index 7d027141..313a7f45 100644 --- a/docs/how-to/backup-to-a-removable-drive-or-an-intermittent-server.md +++ b/docs/how-to/backup-to-a-removable-drive-or-an-intermittent-server.md @@ -82,7 +82,7 @@ before_actions: option in the `hooks:` section of your configuration. Prior to version 1.7.0 Use -`before_create` or similar instead of `before_actions`, which was introduced in +`before_backup` or similar instead of `before_actions`, which was introduced in borgmatic 1.7.0. What this does is check if the `findmnt` command errors when probing for a diff --git a/docs/reference/configuration/command-hooks.md b/docs/reference/configuration/command-hooks.md index 8c4ef3ff..e05fdad1 100644 --- a/docs/reference/configuration/command-hooks.md +++ b/docs/reference/configuration/command-hooks.md @@ -33,7 +33,7 @@ commands: Each command in the `commands:` list has the following options: * `before` or `after`: Name for the point in borgmatic's execution that the commands should be run before or after, one of: - * `action` runs before or after each action for each repository. This replaces the deprecated `before_create`, `after_prune`, etc. + * `action` runs before or after each action for each repository. This replaces the deprecated `before_backup`, `after_prune`, etc. * `repository` runs before or after all actions for each repository. This replaces the deprecated `before_actions` and `after_actions`. * `configuration` runs before or after all actions and repositories in the current configuration file. * `everything` runs before or after all configuration files. Errors here do not trigger `error` hooks or the `fail` state in monitoring hooks. This replaces the deprecated `before_everything` and `after_everything`.