|
| 1 | +# Green.Durham.Grass.and.Herb — Separate Repository |
| 2 | + |
| 3 | +**This module is not a regular directory in this repo. It is a git submodule — it has its own repository.** |
| 4 | + |
| 5 | +## What's going on |
| 6 | + |
| 7 | +The path `modules/Green.Durham.Grass.and.Herb` is a **git submodule** (a gitlink, |
| 8 | +tree mode `160000`), not normal files. It is the only submodule in this repo; every |
| 9 | +other entry under `modules/` is an ordinary directory. |
| 10 | + |
| 11 | +Because this repo has no `.gitmodules` file, git has no URL to resolve the submodule |
| 12 | +against, so GitHub shows it as an empty/broken entry and a fresh checkout leaves an |
| 13 | +empty directory. The content lives in its own repository (see link below). |
| 14 | + |
| 15 | +## Pointer details |
| 16 | + |
| 17 | +- **Submodule path:** `modules/Green.Durham.Grass.and.Herb` |
| 18 | +- **Pinned subproject commit:** `e8d1fa05d4c4f45c99836cd6998d1c2a2d1b7cff` |
| 19 | +- **Upstream repository (its own repo):** |
| 20 | + https://github.com/mearvk/Green.Durham.Grass.and.Herb |
| 21 | + |
| 22 | +> Note: the upstream URL above is the expected location based on the module name and |
| 23 | +> this account's naming convention. If the submodule actually lives elsewhere, update |
| 24 | +> the link here (and, when ready, add a matching `.gitmodules` entry). |
| 25 | +
|
| 26 | +## To check it out locally |
| 27 | + |
| 28 | +```sh |
| 29 | +# If/when a .gitmodules entry exists: |
| 30 | +git submodule update --init modules/Green.Durham.Grass.and.Herb |
| 31 | + |
| 32 | +# Or clone it directly as its own repo: |
| 33 | +git clone https://github.com/mearvk/Green.Durham.Grass.and.Herb.git |
| 34 | +cd Green.Durham.Grass.and.Herb |
| 35 | +git checkout e8d1fa05d4c4f45c99836cd6998d1c2a2d1b7cff |
| 36 | +``` |
0 commit comments