Added a comment: testremote cleanup
This commit is contained in:
parent
3cd2a075b9
commit
86e0e8fce1
1 changed files with 16 additions and 0 deletions
|
@ -0,0 +1,16 @@
|
|||
[[!comment format=mdwn
|
||||
username="Ilya_Shlyakhter"
|
||||
avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0"
|
||||
subject="testremote cleanup"
|
||||
date="2022-08-28T20:15:38Z"
|
||||
content="""
|
||||
>Like the man page for this command says, it's best to make a new remote for testing purposes, not use a production one.
|
||||
|
||||
My fault for not re-reading the webpage.
|
||||
|
||||
There's some value, I think, in being able to test production remotes. There's always a chance that a test remote got configured differently than a production one, so there's more confidence from having tested the production remote.
|
||||
|
||||
If [find/prefer keys by file extension in key](https://git-annex.branchable.com/todo/find__47__prefer_keys_by_file_extension_in_key/) could be implemented, one could delete keys matching `*.this-is-a-test-key`.
|
||||
|
||||
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue