1
0
Fork 0
mirror of synced 2024-12-22 06:31:07 -05:00

Merge pull request #322 from erijo/pages-new-clone

This commit is contained in:
Tim Byrne 2021-03-22 13:44:41 -05:00
commit 5b3e5de331
No known key found for this signature in database
GPG key ID: 14DB4FC2465A4B12
3 changed files with 14 additions and 24 deletions

View file

@ -22,10 +22,10 @@ Clone your existing repo using yadm.
yadm clone <url> yadm clone <url>
yadm status yadm status
The `clone` command will attempt to `merge` your existing repository, but if it The `clone` command will attempt to check out all files that exist in the
fails, it will `stash` any conflicting data. See repository. If a file already exists locally and has content that differs from
[this question](faq#i-just-cloned-my-repository-and-conflicting-data-was-overwritten-why) the one in the repository, the local file will be left unmodified and you'll
in the FAQ if you need help. have to review and resolve the differences.
--- ---

View file

@ -167,6 +167,16 @@ if command -v vim >/dev/null 2>&1; then
fi fi
``` ```
### Bootstrap directory
By installing this [contributed bootstrap][bootstrap.d] script as the bootstrap
program, it is possible to split the bootstrap process into separate
scripts. Each script is placed in `$HOME/.config/yadm/bootstrap.d` and it is
possible to use the [alternate files](/docs/alternates) system to control which
systems that a specific bootstrap step is executed on.
[bootstrap.d]: https://raw.githubusercontent.com/TheLocehiliosan/yadm/master/contrib/bootstrap/bootstrap-in-dir
--- ---
_If you have suggestions for useful bootstrapping logic, let me know..._ _If you have suggestions for useful bootstrapping logic, let me know..._

View file

@ -8,17 +8,6 @@ permalink: /docs/faq
## Usage ## Usage
### I just cloned my repository and conflicting data was overwritten. Why?
Prior to cloning your repository, files managed by yadm already existed. For
example, imagine you are logged into a system and `$HOME/.bash_profile` already
exists. If you then clone your yadm repository—which also contains
`.bash_profile`—then you will likely get a conflict. Since version 1.07,
yadm responds by "stashing" these conflicts. To view the stashed data, you can
run `yadm stash show -p` from within your `$HOME` directory. If you want to
restore the stashed data, you can run `yadm stash apply` from within your
`$HOME` directory.
### While committing I got the message, _"Please tell me who you are"_. Why? ### While committing I got the message, _"Please tell me who you are"_. Why?
Whenever a Git commit is generated, Git requires information about the author of Whenever a Git commit is generated, Git requires information about the author of
@ -45,15 +34,6 @@ yadm gitconfig "user.name" "Alternate Name"
Note: Configuring these settings directly in the yadm repo will require you Note: Configuring these settings directly in the yadm repo will require you
to configure it each time you clone the repo. to configure it each time you clone the repo.
### Why was I prompted to login twice while cloning my repo?
yadm needs to query your repo to determine the default branch used. When you are
using a private repository, this additional query also requires authentication.
You can avoid the double login by specifying which branch to clone using the
`-b` option.
yadm clone -b <branch> <url>
### How can I display untracked files with a `yadm status` command? ### How can I display untracked files with a `yadm status` command?
By default, yadm is configured to ignore untracked files when displaying a By default, yadm is configured to ignore untracked files when displaying a