You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've recently started experimenting with DVC, and one of the first things I noticed is that *.dvc files are created as part of tracking files and directories in DVC.
I believe it would be more efficient and user-friendly if these files were stored in a dedicated directory, such as ./.dvc/some_new_tracking_data_directory, which could then be committed to a version control system (Git, Mercurial, Sapling, etc.).
When comparing DVC to other version control tools like Git and Mercurial, these tools typically store tracking data in a specific hidden directory (e.g., .git, .hg), rather than spreading files throughout the working directory. This keeps the workspace clean and avoids the introduction of unexpected files that other tools or users might not expect.
In short, other, similar tools manage tracking data differently, and I feel DVC’s current approach could benefit from following this convention more closely.
This discussion was converted from issue #10568 on September 26, 2024 18:01.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I've recently started experimenting with DVC, and one of the first things I noticed is that *.dvc files are created as part of tracking files and directories in DVC.
I believe it would be more efficient and user-friendly if these files were stored in a dedicated directory, such as ./.dvc/some_new_tracking_data_directory, which could then be committed to a version control system (Git, Mercurial, Sapling, etc.).
When comparing DVC to other version control tools like Git and Mercurial, these tools typically store tracking data in a specific hidden directory (e.g., .git, .hg), rather than spreading files throughout the working directory. This keeps the workspace clean and avoids the introduction of unexpected files that other tools or users might not expect.
In short, other, similar tools manage tracking data differently, and I feel DVC’s current approach could benefit from following this convention more closely.
Thank you for considering this suggestion!
Beta Was this translation helpful? Give feedback.
All reactions