Ok so if I understand it correctly as of right now in all borgmatic actions, global_arguments.dry_run is checked, ie the presence of a --dry-run flag from argparse arguments, if present then…
I have made the requested changes and added version check before using --dry-run flag for borg compact.
If you haven't started the PR work for this yet, I'd be happy to take it on.
Edits to config and then passing the relevant flags to borg prune.
It's already being taken care of here,…
First: This requires only edits to to config right? Add those two options to the rest of the [bunch](https://projects.torsion.org/VandalByte/borgmatic/commit/fdb08b6c56b7e2697b3b98e98b42a3d82763b07…
a573e606a5
Add a "states" option to command hooks, so you can optionally skip an "after" hook if borgmatic encounters an error (#1066).
81db67c759
Fix a regression in monitoring hooks in which an error pinged the finish state instead of the fail state (#1065).
Yes, I was getting Assertion Error in tests, LSH != RSH, I looked for any way to omit in schema.yaml, But now I [see](https://projects.torsion.org/borgmatic-collective/borgmatic/commit/f6de79060e…
929d343214
Add CLI flags for every config option and add config options for many action flags (#303).
9ea55d9aa3
Add a documentation note about a limitation: You can't pass flags as values to flags (#303).
3eabda45f2
If a boolean option name already starts with "no_", don't add a "--no-no-..." CLI flag (#303).