docs: update pr and pr_commits and domain_layer_model (#521)

* docs: update pr and pr_commits and domain_layer_model * docs: all version adapt schema-diagram
apache · May 11, 2023 · 60fbfaf · 60fbfaf
1 parent 079be9f
commit 60fbfaf
Show file tree

Hide file tree

Showing 14 changed files with 57,490 additions and 19,943 deletions.
diff --git a/docs/DataModels/DevLakeDomainLayerSchema.md b/docs/DataModels/DevLakeDomainLayerSchema.md
diff --git a/static/img/DomainLayerSchema/domain_layer_model.ndm2 b/static/img/DomainLayerSchema/domain_layer_model.ndm2
diff --git a/static/img/DomainLayerSchema/domain_layer_model_v0.17-beta3.ndm2 b/static/img/DomainLayerSchema/domain_layer_model_v0.17-beta3.ndm2
diff --git a/.../img/DomainLayerSchema/schema-diagram.png → ...omainLayerSchema/schema-diagram-v0.14.png b/.../img/DomainLayerSchema/schema-diagram.png → ...omainLayerSchema/schema-diagram-v0.14.png
diff --git a/static/img/DomainLayerSchema/schema-diagram-v0.15.svg b/static/img/DomainLayerSchema/schema-diagram-v0.15.svg
diff --git a/static/img/DomainLayerSchema/schema-diagram-v0.16.png b/static/img/DomainLayerSchema/schema-diagram-v0.16.png
diff --git a/static/img/DomainLayerSchema/schema-diagram-v0.17-beta3.svg b/static/img/DomainLayerSchema/schema-diagram-v0.17-beta3.svg
diff --git a/static/img/DomainLayerSchema/schema-diagram.svg b/static/img/DomainLayerSchema/schema-diagram.svg
diff --git a/versioned_docs/version-v0.11/DataModels/DevLakeDomainLayerSchema.md b/versioned_docs/version-v0.11/DataModels/DevLakeDomainLayerSchema.md
@@ -30,7 +30,7 @@ This is the up-to-date domain layer schema for DevLake v0.10.x. Tables (entities
 
 
 ### Schema Diagram
-![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram.png)
+![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram-v0.14.png)
 
 When reading the schema, you'll notice that many tables' primary key is called `id`. Unlike auto-increment id or UUID, `id` is a string composed of several parts to uniquely identify similar entities (e.g. repo) from different platforms (e.g. Github/Gitlab) and allow them to co-exist in a single table.
 

diff --git a/versioned_docs/version-v0.12/DataModels/DevLakeDomainLayerSchema.md b/versioned_docs/version-v0.12/DataModels/DevLakeDomainLayerSchema.md
@@ -30,7 +30,7 @@ This is the up-to-date domain layer schema for DevLake v0.10.x. Tables (entities
 
 
 ### Schema Diagram
-![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram.png)
+![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram-v0.14.png)
 
 When reading the schema, you'll notice that many tables' primary key is called `id`. Unlike auto-increment id or UUID, `id` is a string composed of several parts to uniquely identify similar entities (e.g. repo) from different platforms (e.g. Github/Gitlab) and allow them to co-exist in a single table.
 

diff --git a/versioned_docs/version-v0.13/DataModels/DevLakeDomainLayerSchema.md b/versioned_docs/version-v0.13/DataModels/DevLakeDomainLayerSchema.md
@@ -31,7 +31,7 @@ This is the up-to-date domain layer schema for DevLake v0.10.x. Tables (entities
 
 
 ### Schema Diagram
-![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram.png)
+![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram-v0.14.png)
 
 When reading the schema, you'll notice that many tables' primary key is called `id`. Unlike auto-increment id or UUID, `id` is a string composed of several parts to uniquely identify similar entities (e.g. repo) from different platforms (e.g. Github/Gitlab) and allow them to co-exist in a single table.
 

diff --git a/versioned_docs/version-v0.14/DataModels/DevLakeDomainLayerSchema.md b/versioned_docs/version-v0.14/DataModels/DevLakeDomainLayerSchema.md
@@ -31,7 +31,7 @@ This is the up-to-date domain layer schema for DevLake v0.10.x. Tables (entities
 
 
 ### Schema Diagram
-[![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram.png)](/img/DomainLayerSchema/schema-diagram.png)
+[![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram-v0.14.png)](/img/DomainLayerSchema/schema-diagram-v0.14.png)
 
 When reading the schema, you'll notice that many tables' primary key is called `id`. Unlike auto-increment id or UUID, `id` is a string composed of several parts to uniquely identify similar entities (e.g. repo) from different platforms (e.g. Github/Gitlab) and allow them to co-exist in a single table.
 

diff --git a/versioned_docs/version-v0.15/DataModels/DevLakeDomainLayerSchema.md b/versioned_docs/version-v0.15/DataModels/DevLakeDomainLayerSchema.md
@@ -34,7 +34,7 @@ This is the up-to-date domain layer schema for DevLake v0.10.x. Tables (entities
 
 ### Schema Diagram
 
-[![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram.svg)](/img/DomainLayerSchema/schema-diagram.svg)
+[![Domain Layer Schema](/img/DomainLayerSchema/schema-diagram-v0.15.svg)](/img/DomainLayerSchema/schema-diagram-v0.15.svg)
 
 When reading the schema, you'll notice that many tables' primary key is called `id`. Unlike auto-increment id or UUID, `id` is a string composed of several parts to uniquely identify similar entities (e.g. repo) from different platforms (e.g. Github/Gitlab) and allow them to co-exist in a single table.
 

diff --git a/versioned_docs/version-v0.17/DataModels/DevLakeDomainLayerSchema.md b/versioned_docs/version-v0.17/DataModels/DevLakeDomainLayerSchema.md