Skip to content

Commit

Permalink
README: add a helpful note for people who _already_ cloned
Browse files Browse the repository at this point in the history
The advice to use Scalar comes too late for contributors who already
have obtained a (full) clone. To help them, let's just suggest to
convert the checkout into a sparse one.

Suggested-by: Toon Claes <toon@iotcl.com>
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
  • Loading branch information
dscho committed Oct 17, 2024
1 parent b7c5d89 commit 643b333
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,8 @@ $ cd git-scm.com
$ git sparse-checkout set layouts content static assets hugo.yml data script
$ git reset --hard
```
> [!NOTE]
> If you _already_ have a full clone and wish to accelerate development by focusing only on a small subset of the pages, you may want to run the `git sparse-checkout set [...]` command mentioned above.
Here is a detailed list of the relevant directories:

Expand Down

0 comments on commit 643b333

Please sign in to comment.