-
I have been playing with the example of the vignette, but I don't grasp how gittargets tracks the data status (and revert it when needed): I expected to see a commit specific for each It seems like it uses a git submodule or something similar because when I used
Exploring via the terminal under the _targets folder I see:
Can I combine using git from the terminal and the I see there is a workaround related to .gittatributes |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
The snapshot model is explained at https://docs.ropensci.org/gittargets/articles/git.html#snapshot-model. Each snapshot is a commit, those commits are partitioned into branches, and each branch corresponds to a unique code commit. In other words,
You could in theory, but it is much easier to check out the code commit you want and then call |
Beta Was this translation helpful? Give feedback.
The snapshot model is explained at https://docs.ropensci.org/gittargets/articles/git.html#snapshot-model. Each snapshot is a commit, those commits are partitioned into branches, and each branch corresponds to a unique code commit. In other words,
gittargets
uses branching to group the data commits by the corresponding code commits. This is what allows it to revert to a data commit when you revert to an old code commit.