Added a comment
authornobodyinperson <nobodyinperson@web>
Wed, 5 Jul 2023 20:46:13 +0000 (20:46 +0000)
committeradmin <admin@branchable.com>
Wed, 5 Jul 2023 20:46:13 +0000 (20:46 +0000)
doc/todo/option_to_explain/comment_1_81644886e14851a276dc3c89965df62e._comment [new file with mode: 0644]

diff --git a/doc/todo/option_to_explain/comment_1_81644886e14851a276dc3c89965df62e._comment b/doc/todo/option_to_explain/comment_1_81644886e14851a276dc3c89965df62e._comment
new file mode 100644 (file)
index 0000000..b702a50
--- /dev/null
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="nobodyinperson"
+ avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
+ subject="comment 1"
+ date="2023-07-05T20:46:13Z"
+ content="""
+Sounds absolutely awesome! The new `git annex satisfy` would also benefit from this. 
+
+Also when thinking about a potential future `--dry-run` mode that wouldn't actually do stuff but in combination with `--explain` would display what it would do and why. I know dry-running can be nontrivial to implement, especially when actions change state. But imagine how cool it would be to do `git annex assist --dry-run --explain` and to see what exactly it *would* do (what files go to git, which to the annex, what files will be copied where, etc.) ðŸ¤©
+"""]]