If you are familiar with git, oxen should be an easy learning curve.
oxen log
or in the OxenHub dashboard for who changed what.
oxen clone
with no flags will download the latest commit from the main
branch.
-b
flag.
--shallow
flag.
--shallow
flag you will notice no data files in your working directory. You can still see the data on the branch on the remote with the oxen remote
subcommands.
oxen download
. This is useful if you only need a specific set of files and directories for training or testing.
--all
flag. This is handy if you want to pull a full history and push to a new remote, or have a workflow where you need to quickly swap between commits locally. Often for running experiments, training, or testing, all you need is a subset of the data.
oxen add
command and giving a full file path or directory.
status
command.
Note: since we are dealing with large datasets with many files, status
rolls up the changes and summarizes them for you.
-s
(skip) and -l
(limit) params on the status command. Run oxen status --help
for more info.
checkout
command.
restore
command comes in handy if you made some changes locally and you want to revert the changes. This can be used for example if you accidentally delete or modify or stage a file that you did not intend to.
oxen rm
command. Removing data from a commit can be useful if you find errors or simply want to create a smaller subset of data on a separate branch for debugging or testing.
-r
flag.
oxen rm
with the --staged
flag to unstage the file or directory.