Files
Adrian Duke 0684d1ccdf cli: Changed the default scope from all to followed for clone and seed
The previous implementation used 'all' as the default for scope, this
could lead to surprising behaviour where a user would fetch all
references for cloned and seeded repositories. Instead have a progressive,
safe by default value - where it fetches only 'followed' references. Later
a user can decide to set the scope to 'all'. NOTE: the default policy
scope was not changed from 'all' and is intended to be changed at a
later date.
2026-02-16 21:39:11 +01:00

1.1 KiB

Using rad clone is useful if we want to create and fetch a project that exists on Radicle, but perhaps we're in a scenario where we may already have an existing Git repository and so a full clone is not necessary.

Instead, we want to fetch the project from the network into our local storage. In this scenario, we know that the project is rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji. In order to fetch it, we first have to update our seeding policy for the project.

$ rad seed rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji --no-fetch
✓ Seeding policy updated for rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji with scope 'followed'

Now that the project is seeding we can fetch it and we will have it in our local storage. Note that the seed command can also be told to fetch by passing the --fetch option.

$ rad sync --fetch rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji
Fetching rad:z42hL2jL4XNk6K8oHQaSWfMgCL7ji from the network, found 1 potential seed(s).
✓ Target met: 1 seed(s)
🌱 Fetched from z6MknSLrJoTcukLrE435hVNQT4JUhbvWLX4kUzqkEStBU8Vi

However, we don't have a local fork of the project. We can follow this up with rad-fork.