This is an automated email from the ASF dual-hosted git repository.
abeizn pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
The following commit(s) were added to refs/heads/main by this push:
new d88a6cf11d docs: fix incorrect desc in the domain layer doc (#684)
d88a6cf11d is described below
commit d88a6cf11dc74349783bf3ee7a5277527d5b0e2e
Author: Louis.z <[email protected]>
AuthorDate: Thu Dec 7 14:52:51 2023 +0800
docs: fix incorrect desc in the domain layer doc (#684)
Co-authored-by: Startrekzky <[email protected]>
---
docs/DataModels/DevLakeDomainLayerSchema.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/DataModels/DevLakeDomainLayerSchema.md
b/docs/DataModels/DevLakeDomainLayerSchema.md
index f04d9615ef..7146066b72 100644
--- a/docs/DataModels/DevLakeDomainLayerSchema.md
+++ b/docs/DataModels/DevLakeDomainLayerSchema.md
@@ -223,7 +223,7 @@ A `board` is an issue list or a collection of issues. It's
the abstraction of a
| `id` | varchar | 255 | A board's `id` is composed of "<
plugin >:< Entity >:< PK0 >[:PK1]..." <ul><li>For a Github repo's issue list,
the board id is like "< github >:< GithubRepos >:< ConnectionId >:<
GithubRepoId >".<br/>E.g. "github:GithubRepo:384111310"</li> <li>For a Jira
Board, the id is like "< jira >:< JiraSourceId >< JiraBoards >:< ConnectionId
>:< JiraBoardsId >".<br/>E.g. "jira:1:JiraBoards:1:12"</li></ul> | PK |
| `name` | varchar | 255 | The name of the board. Note: the
board name of a Github repo 'apache/incubator-devlake' is
'apache/incubator-devlake', representing the [default issue
list](https://github.com/apache/incubator-devlake/issues).
| |
| `description` | varchar | 255 | The description of the board.
| |
-| `url` | varchar | 255 | The url of the board. E.g.
https://github.com/apache/incubator-devlake
| |
+| `url` | varchar | 255 | The url of the board. E.g.
https://github.com/apache/incubator-devlake/issues
| |
| `created_date` | datetime | 3 | Board creation time
| |
| `type` | varchar | 255 | Identify scrum and non-scrum board
| |
@@ -508,7 +508,7 @@ A cicd_pipeline is the abstraction of a top-level CI/CD
execution, e.g. a GitHub
| `pipeline_id` | varchar | 255 | This key is generated based on
details from the original plugin | PK |
| `commit_sha` | varchar | 255 | The commit that triggers this
pipeline | PK |
| `branch` | varchar | 255 | The branch that triggers this
pipeline | |
-| `repo` | varchar | 255 |
| |
+| `repo_url` | varchar | 255 |
| |
| `repo_id` | varchar | 255 | The repo that this pipeline belongs
to | |
#### cicd_tasks
