Introduce git helpers?
See original GitHub issueFor #2856 , should we introduce some of the existing options to reduce friction with Git? In particular:
core.autostage
: staging changes to DVC files.install
: install hooks for checkout, commit, and push.
These options might be too in-depth for getting started, but they also seem hard to find today despite being useful for many (maybe most) users to reduce the pain of duplicating DVC and Git commands.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:17 (17 by maintainers)
Top Results From Across the Web
An introduction to Git: what it is, and how to use it
Our mission: to help people learn to code for free. We accomplish this by creating thousands of videos, articles, and interactive coding lessons ......
Read more >gittutorial Documentation - Git SCM
This tutorial explains how to import a new project into Git, make changes to it, and share changes with other developers. If you...
Read more >Introduction to Git and GitHub - W3Schools
What does Git do? · Manage projects with Repositories · Clone a project to work on a local copy · Control and track...
Read more >About Git - GitHub Docs
Basic Git commands · git init initializes a brand new Git repository and begins tracking an existing directory. · git clone creates a...
Read more >Developing a Custom Remote Git Helper - Apriorit
When a remote helper uses the standard transfer protocol, it needs to implement only the connect capability. Remote helpers establish a ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Related: https://github.com/iterative/dvc/discussions/6929.
That wasn’t initially my question, but it’s a good question. First, it’s probably more applicable to
autostage
thandvc install
.dvc install
reduces DVC commands, not Git commands.Even for
autostage
, I wouldn’t rush to do this. It would be a big change and one that might not make sense for users who miss that part or who started using DVC before we made the change. Also, glancing through the examples, I think the Git commands are mostly helpful by showing when.dvc
or.gitignore
files were modified.When I mentioned lowering the barrier to entry, it could be by eventually eliminating these Git commands and not bothering to explain
.dvc
files and the details of how DVC works at first, but I’m not so sure I even like that idea, and I don’t think we should go that far now.I think #72 can cover things like this? Especially if we mention about that sections in the very beginning (put a link into the User Guide tile for example in the index page)?