2016-09-06 23:19:16 -04:00
|
|
|
---
|
|
|
|
|
title: "Getting Started"
|
|
|
|
|
permalink: /docs/getting_started
|
|
|
|
|
---
|
2019-10-19 14:59:03 -04:00
|
|
|
Starting out with yadm should be just a few easy steps.
|
2016-09-06 23:19:16 -04:00
|
|
|
|
|
|
|
|
### If you don't currently have a repository
|
|
|
|
|
Start out with an empty local repository
|
|
|
|
|
|
|
|
|
|
yadm init
|
|
|
|
|
yadm add <important file>
|
|
|
|
|
yadm commit
|
|
|
|
|
|
|
|
|
|
Eventually you will want to push the local repo to a remote.
|
|
|
|
|
|
|
|
|
|
yadm remote add origin <url>
|
|
|
|
|
yadm push -u origin master
|
|
|
|
|
|
|
|
|
|
### If you have an existing remote repository
|
2019-10-19 14:59:03 -04:00
|
|
|
Clone your existing repo using yadm.
|
2016-09-06 23:19:16 -04:00
|
|
|
|
|
|
|
|
yadm clone <url>
|
|
|
|
|
yadm status
|
|
|
|
|
|
|
|
|
|
The `clone` command will attempt to `merge` your existing repository, but if it
|
2017-01-31 23:09:59 -05:00
|
|
|
fails, it will `stash` any conflicting data. See
|
|
|
|
|
[this question](faq#i-just-cloned-my-repository-and-conflicting-data-was-overwritten-why)
|
2016-09-06 23:19:16 -04:00
|
|
|
in the FAQ if you need help.
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
That's all it takes to start. Now most Git commands can be used as
|
|
|
|
|
`yadm <git command>`.
|
|
|
|
|
Read about [common commands](common_commands) for ideas.
|
