@c4a/context 0.6.7 → 0.6.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -67,6 +67,18 @@ inside Git, because Context must resolve the current commit. A workspace outside
|
|
|
67
67
|
Git must use a literal, already-published prefix without `{commit}`. Context
|
|
68
68
|
appends the project-relative `knowledge/assets/...` path.
|
|
69
69
|
|
|
70
|
+
For a non-GitHub service that exposes raw files through the GitHub-compatible
|
|
71
|
+
same-host layout
|
|
72
|
+
`https://<host>/<namespace>/<repository>/raw/<ref>/<path>`, derive and configure
|
|
73
|
+
the explicit prefix before choosing bundled delivery. For example, use
|
|
74
|
+
`https://git.example.com/team/knowledge/raw/{commit}` for a workspace at the
|
|
75
|
+
repository root. If the workspace is nested, append its repository-relative
|
|
76
|
+
directory to the prefix because Context appends only the project-relative
|
|
77
|
+
`knowledge/assets/...` path. This derivation is appropriate only when the
|
|
78
|
+
service's raw convention and repository identity are confirmed; otherwise ask
|
|
79
|
+
for the prefix or use bundled delivery. The fact that Context does not
|
|
80
|
+
automatically recognize a host is not, by itself, a reason to bundle.
|
|
81
|
+
|
|
70
82
|
The resolved commit and raw URL participate in package freshness, so changing
|
|
71
83
|
Git HEAD or the selected remote makes an existing package stale. Context does
|
|
72
84
|
not check whether resources are committed, pushed, or remotely readable;
|