docs: add fork banner to .github/README.md (GitHub profile-README convention)
Matches the banner already on the root README.md -- this file is otherwise upstream heartwood's own GitHub-specific profile readme, unrelated to and predating the LFS-over-IPFS work, so someone landing on it directly (or via GitHub's own rendering convention) had no indication this repo is a fork with different setup instructions.
This commit is contained in:
parent
3ad836577a
commit
2306aabc4a
|
|
@ -1,5 +1,16 @@
|
|||
# ❤️🪵
|
||||
|
||||
> ## Fork: Git LFS support, backed by IPFS
|
||||
>
|
||||
> This is a fork of upstream [`radicle-dev/heartwood`](https://github.com/radicle-dev/heartwood)
|
||||
> adding Git LFS (large file) support, with large file content stored on each contributor's own
|
||||
> local IPFS node rather than a central server. Everything below is upstream's own text,
|
||||
> unchanged, and describes upstream `heartwood` in general, not this fork specifically.
|
||||
>
|
||||
> This repository is developed on a self-hosted Forgejo instance, not GitHub — see
|
||||
> [the main `README.md`](../README.md) for the fork's own quickstart, and
|
||||
> [`LFS-IPFS.md`](../LFS-IPFS.md) for the full design, encryption details, and troubleshooting.
|
||||
|
||||
*Radicle Heartwood Protocol & Stack*
|
||||
|
||||
Heartwood is the third iteration of the Radicle Protocol, a powerful
|
||||
|
|
|
|||
Loading…
Reference in New Issue