You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,14 +17,20 @@
17
17
18
18
## Introduction
19
19
20
-
This repository is meant to hold lightweight metadata for shared Nabla assets and CI references without forcing large binary payloads into normal Git history.
20
+
This repository provides the NAM consumer module together with the first-party
21
+
Nabla manifest registry and release-backed payload channels, without forcing
22
+
large binary payloads into normal Git history.
21
23
22
24
The repository itself is first-party Nabla infrastructure, but the consumer
23
25
module is not meant to be Nabla-only. Other projects can vendor
24
26
`nam.cmake`, keep their own `.dvc`-based manifest repository, publish payloads
25
27
through `GitHub Release assets`, and reuse the same build-time materialization
26
28
model.
27
29
30
+
Current scope is intentionally narrow. For now the only supported remote
31
+
payload backend is `GitHub Release assets`, and no additional backends are
message(FATAL_ERROR"NablaAssetManifests: failed to query release metadata for `${NAM_REPO}` tag `${NAM_TAG}` after 3 attempts, last status `${_last_status_code}`")
0 commit comments