mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2022-08-03 09:53:56 -04:00
commit c6ce2150f4
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
doc/todo/add_--dry-run.mdwn Normal file
View file

@ -0,0 +1,24 @@
Previous discussion which touched upon it was [7 years ago](https://git-annex.branchable.com/todo/wishlist__58___--dry-run_option_for_all_commands/) (unless I missed some) where part of the response was
> I don't see the benefit to justify this work. git annex add is entirely predictable; it's very similar to git add. Which itself lacks a dry-run option.
Oh well:
```
$> git add --help | grep -e '-n, --dry' -A1
-n, --dry-run
Don’t actually add the file(s), just show if they exist and/or will be ignored.
```
and users [submit requests against DataLad](https://github.com/datalad/datalad/issues/6909) to be able to discover what file would go to git and which to git-annex. Also would be useful to know if to git-annex -- would it be locked or unlocked? Someone else might even want to discover what would be the annex key if it would go into annex, but so far I do not think it is within our desired use-case and it might be too lengthy to compute the key checksum etc.
As for
> And like git add, you can certianly undo the effects of git annex add.
well -- unless there was a version staged already you don't want to loose etc.
[[!meta author=yoh]]
[[!tag projects/datalad]]