From b8e4e66a2e3e864e54bd0b3dd44017ce7a1b8d33 Mon Sep 17 00:00:00 2001 From: "restyled-io[bot]" <32688539+restyled-io[bot]@users.noreply.github.com> Date: Mon, 29 Jun 2020 16:32:37 -0700 Subject: [PATCH] Restyled by prettier (#1513) Co-authored-by: Restyled.io --- content/blog/2020-06-29-june-20-community-gems.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/blog/2020-06-29-june-20-community-gems.md b/content/blog/2020-06-29-june-20-community-gems.md index b781f5444d..3b52df6dbc 100644 --- a/content/blog/2020-06-29-june-20-community-gems.md +++ b/content/blog/2020-06-29-june-20-community-gems.md @@ -41,11 +41,11 @@ _Just like this but with technical documentation._ ### Q: After I pushed my local data to remote storage, I noticed the file names are different in my storage repository- they're hash values. [Can I make them more meaningful names?](https://discord.com/channels/485586884165107732/563406153334128681/717737163122540585) No, but for a good reason! What you're seeing are cached files, and they're -stored with a special naming convention that makes DVC versioning and addressing possible- -these file names are how DVC deduplicates data (to avoid keeping multiple copies -of the same file version) and ensures that each unique version of a file is -immutable. If you manually overwrote those filenames you would risk breaking Git -version control. You can +stored with a special naming convention that makes DVC versioning and addressing +possible- these file names are how DVC deduplicates data (to avoid keeping +multiple copies of the same file version) and ensures that each unique version +of a file is immutable. If you manually overwrote those filenames you would risk +breaking Git version control. You can [read more about how DVC uses this file format in our docs](https://dvc.org/doc/user-guide/dvc-files-and-directories#structure-of-cache-directory). It sounds like you're looking for ways to interact with DVC-tracked objects at a