Files
heartwood/crates/radicle-cli/examples/rad-init-with-existing-remote.md
T
Lorenz Leutgeb 5bc2dc677b repo: Move workspace crates into crates subdirectory
This keeps the top level of the repo cleaner, e.g.
<https://github.com/radicle-dev/heartwood> scrolls less and
<https://app.radicle.xyz/nodes/rosa.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/>
might show more files at the top level.

This way we also don't have to explicitly name all crates in
`Cargo.toml`.
2025-06-09 15:09:21 +02:00

1007 B

Let's try to rad init a repo which already has a remote tracking branch for master.

First we have to create a valid remote repository.

$ git init --bare remote
Initialized empty Git repository in [..]

Then we add it as a remote.

$ git remote add origin file://$PWD/remote
$ git push -u origin master:master
...
$ git branch -vv
* master f2de534 [origin/master] Second commit

Then we initialize.

$ rad init --name heartwood --description "Heartwood Protocol & Stack" --no-confirm --public

Initializing public radicle 👾 repository in [..]

✓ Repository heartwood created.

Your Repository ID (RID) is rad:z2D6wQnKapY7dn5meBnbH2rUKNZbT.
You can show it any time by running `rad .` from this directory.

Your repository will be announced to the network when you start your node.
You can start your node with `rad node start`.
To push changes, run `git push rad master`.

Finally we run the suggested command.

$ git push rad master
Everything up-to-date