This is an automated email from the ASF dual-hosted git repository.
zky 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 df1407592a ci: fix missing checks caused by github rate limit (#497)
df1407592a is described below
commit df1407592a01dd52f91f587973a65ea76bc59939
Author: Bird <[email protected]>
AuthorDate: Wed Apr 26 14:16:54 2023 +0800
ci: fix missing checks caused by github rate limit (#497)
Signed-off-by: Bird <[email protected]>
---
.asf.yaml | 4 +++
.github/workflows/pr_ci.yaml | 2 +-
.lycheeignore | 3 ++
docs/DeveloperManuals/PluginImplementation.md | 2 +-
docs/Plugins/refdiff.md | 2 +-
.../DataModels/DevLakeDomainLayerSchema.md | 2 +-
versioned_docs/version-v0.11/EngineeringMetrics.md | 38 +++++++++++-----------
.../DataModels/DevLakeDomainLayerSchema.md | 2 +-
versioned_docs/version-v0.12/EngineeringMetrics.md | 38 +++++++++++-----------
.../DataModels/DevLakeDomainLayerSchema.md | 2 +-
.../DeveloperManuals/PluginImplementation.md | 2 +-
versioned_docs/version-v0.15/Plugins/refdiff.md | 2 +-
.../DeveloperManuals/PluginImplementation.md | 2 +-
versioned_docs/version-v0.16/Plugins/refdiff.md | 2 +-
14 files changed, 55 insertions(+), 48 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index 4ae7273235..3b9556afb4 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -38,6 +38,10 @@ github:
dismiss_stale_reviews: true
require_code_owner_reviews: true
required_approving_review_count: 1
+ # The triage role allows people to assign, edit, and close issues and pull
requests,
+ # without giving them write access to the code.
+ collaborators:
+ - aFlyBird0
publish:
whoami: asf-site
diff --git a/.github/workflows/pr_ci.yaml b/.github/workflows/pr_ci.yaml
index 4df65845f7..5d503fe478 100644
--- a/.github/workflows/pr_ci.yaml
+++ b/.github/workflows/pr_ci.yaml
@@ -47,4 +47,4 @@ jobs:
# 'build': the site directory to check
# './*.md': all markdown files in the root directory
- lychee -E -i -n -t 45 --max-concurrency 64 -a 429,401,403 -m 10 --
'build' '*.md'
+ lychee -E -i -n -t 45 --max-concurrency 64 -a 401,403 -m 10 --
'build' '*.md'
diff --git a/.lycheeignore b/.lycheeignore
index e8a377ac9a..06c684e9b3 100644
--- a/.lycheeignore
+++ b/.lycheeignore
@@ -6,5 +6,8 @@ https://www.google-analytics.com
.*xxx.*
https://twitter.com/ApacheDevLake
https://merico.feishu.cn.*
+.*edit/main.*
+.*sample-url.*
https://github.com/dailidong
+
diff --git a/docs/DeveloperManuals/PluginImplementation.md
b/docs/DeveloperManuals/PluginImplementation.md
index 38c08b494b..3af7aced19 100644
--- a/docs/DeveloperManuals/PluginImplementation.md
+++ b/docs/DeveloperManuals/PluginImplementation.md
@@ -35,7 +35,7 @@ A plugin mainly consists of a collection of subtasks that can
be executed by Dev
2.
[PluginInit](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_init.go)
allows a plugin to customize its initialization
3.
[PluginTask](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_task.go)
enables a plugin to prepare data prior to subtask execution
4.
[PluginApi](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_api.go)
lets a plugin exposes some self-defined APIs
-5.
[PluginMigration](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_migration.go)
is where a plugin manages its database migrations
+5.
[PluginMigration](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_migration.go)
is where a plugin manages its database migrations
6.
[PluginModel](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_model.go)
allows other plugins to get the model information of all database tables of
the current plugin through the GetTablesInfo() method. If you need to access
Domain Layer Models, please visit
[DomainLayerSchema](https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema/)
7.
[PluginBlueprint](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_blueprint.go)
is the foundation for Blueprint and Plugin to collaborate and generate a
reasonable Pipeline Plan based on User Settings. For example, a user may
declare that he/she wants to collect data from a GitHub Repo, which implies
that not only the issues and PRs, but also the git-meta-data including commits
history, branches, tags, etc. need to be collected. To do it and do it fast
[...]
diff --git a/docs/Plugins/refdiff.md b/docs/Plugins/refdiff.md
index 7c8b5d0b63..d4908c07d6 100644
--- a/docs/Plugins/refdiff.md
+++ b/docs/Plugins/refdiff.md
@@ -8,7 +8,7 @@ description: >
RefDiff is a plugin that performs calculation tasks and has 2 main purposes.
-- Calculate the difference in commits between releases/tags to [analyze the
amount of code in each
release](https://github.com/apache/incubator-devlake/blob/main/plugins/refdiff/tasks/commit_diff_calculator.go)
+- Calculate the difference in commits between releases/tags to [analyze the
amount of code in each
release](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/refdiff/tasks/commit_diff_calculator.go)
- Calculate the difference in commits between deployments to [calculate DORA
metrics](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/refdiff/tasks/deployment_commit_diff_calculator.go)
And the output of RefDiff is stored in the table commits_diffs,
finished_commits_diffs, ref_commits.
diff --git
a/versioned_docs/version-v0.11/DataModels/DevLakeDomainLayerSchema.md
b/versioned_docs/version-v0.11/DataModels/DevLakeDomainLayerSchema.md
index 0def821a58..40dc18255b 100644
--- a/versioned_docs/version-v0.11/DataModels/DevLakeDomainLayerSchema.md
+++ b/versioned_docs/version-v0.11/DataModels/DevLakeDomainLayerSchema.md
@@ -329,7 +329,7 @@ A pull request is the abstraction of Github pull request
and Gitlab merge reques
| `title` | varchar | 255 | The title of pull request
| |
| `description` | longtext | | The body/description of pull
request
| |
| `status` | varchar | 255 | the status of pull requests.
For a Github pull request, the status can either be 'open' or 'closed'.
| |
-| `number` | varchar | 255 | The number of PR. Eg, 1536 is
the number of this [PR](https://github.com/merico-dev/lake/pull/1563)
| |
+| `number` | varchar | 255 | The number of PR. Eg, 1536 is
the number of this [PR](https://github.com/apache/incubator-devlake/pull/1563)
| |
| `base_repo_id` | varchar | 255 | The repo that will be updated.
| |
| `head_reop_id` | varchar | 255 | The repo containing the changes
that will be added to the base. If the head repository is NULL, this means that
the corresponding project had been deleted when DevLake processed the pull
request.
| |
| `base_ref` | varchar | 255 | The branch name in the base
repo that will be updated
| |
diff --git a/versioned_docs/version-v0.11/EngineeringMetrics.md
b/versioned_docs/version-v0.11/EngineeringMetrics.md
index e05ec1e402..e73c04828a 100644
--- a/versioned_docs/version-v0.11/EngineeringMetrics.md
+++ b/versioned_docs/version-v0.11/EngineeringMetrics.md
@@ -20,7 +20,7 @@ description: >
<td rowspan="10">Delivery Velocity</td>
<td>Requirement Count</td>
<td>Number of issues in type "Requirement"</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td rowspan="2">
1. Analyze the number of requirements and delivery rate of different time
cycles to find the stability and trend of the development process.
<br/>2. Analyze and compare the number of requirements delivered and delivery
rate of each project/team, and compare the scale of requirements of different
projects.
@@ -32,12 +32,12 @@ description: >
<tr>
<td>Requirement Delivery Rate</td>
<td>Ratio of delivered requirements to all requirements</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
</tr>
<tr>
<td>Requirement Lead Time</td>
<td>Lead time of issues with type "Requirement"</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td>
1. Analyze the trend of requirement lead time to observe if it has improved
over time.
<br/>2. Analyze and compare the requirement lead time of each project/team to
identify key projects with abnormal lead time.
@@ -48,7 +48,7 @@ description: >
<tr>
<td>Requirement Granularity</td>
<td>Number of story points associated with an issue</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td>
1. Analyze the story points/requirement lead time of requirements to evaluate
whether the ticket size, ie. requirement complexity is optimal.
<br/>2. Compare the estimated requirement granularity with the actual
situation and evaluate whether the difference is reasonable by combining more
microscopic workload metrics (e.g. lines of code/code equivalents)</td>
@@ -58,7 +58,7 @@ description: >
<tr>
<td>Commit Count</td>
<td>Number of Commits</td>
- <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
+ <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
<td>
1. Identify the main reasons for the unusual number of commits and the
possible impact on the number of commits through comparison
<br/>2. Evaluate whether the number of commits is reasonable in conjunction
with more microscopic workload metrics (e.g. lines of code/code
equivalents)</td>
@@ -68,7 +68,7 @@ description: >
<tr>
<td>Added Lines of Code</td>
<td>Accumulated number of added lines of code</td>
- <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
+ <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
<td rowspan="2">
1. From the project/team dimension, observe the accumulated change in Added
lines to assess the team activity and code growth rate
<br/>2. From version cycle dimension, observe the active time distribution of
code changes, and evaluate the effectiveness of project development model.
@@ -79,12 +79,12 @@ description: >
<tr>
<td>Deleted Lines of Code</td>
<td>Accumulated number of deleted lines of code</td>
- <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
+ <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
</tr>
<tr>
<td>Pull Request Review Time</td>
<td>Time from Pull/Merge created time until merged</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
<td>
1. Observe the mean and distribution of code review time from the
project/team/individual dimension to assess the rationality of the review
time</td>
<td>1. Take inventory of project/team code review resources to avoid
lack of resources and backlog of review sessions, resulting in long waiting time
@@ -93,7 +93,7 @@ description: >
<tr>
<td>Bug Age</td>
<td>Lead time of issues in type "Bug"</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td rowspan="2">
1. Observe the trend of bug age and locate the key reasons.<br/>
2. According to the severity level, type (business, functional
classification), affected module, source of bugs, count and observe the length
of bug and incident age.</td>
@@ -103,13 +103,13 @@ description: >
<tr>
<td>Incident Age</td>
<td>Lead time of issues in type "Incident"</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
</tr>
<tr>
<td rowspan="8">Delivery Quality</td>
<td>Pull Request Count</td>
<td>Number of Pull/Merge Requests</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
<td rowspan="3">
1. From the developer dimension, we evaluate the code quality of developers by
combining the task complexity with the metrics related to the number of review
passes and review rounds.<br/>
2. From the reviewer dimension, we observe the reviewer's review style by
taking into account the task complexity, the number of passes and the number of
review rounds.<br/>
@@ -121,24 +121,24 @@ description: >
<tr>
<td>Pull Request Pass Rate</td>
<td>Ratio of Pull/Merge Review requests to merged</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Pull Request Review Rounds</td>
<td>Number of cycles of commits followed by comments/final merge</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Pull Request Review Count</td>
<td>Number of Pull/Merge Reviewers</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
<td>1. As a secondary indicator, assess the cost of labor invested in
the code review process</td>
<td>1. Take inventory of project/team code review resources to avoid
long waits for review sessions due to insufficient resource input</td>
</tr>
<tr>
<td>Bug Count</td>
<td>Number of bugs found during testing</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td rowspan="4">
1. From the project or team dimension, observe the statistics on the total
number of defects, the distribution of the number of defects in each severity
level/type/owner, the cumulative trend of defects, and the change trend of the
defect rate in thousands of lines, etc.<br/>
2. From version cycle dimension, observe the statistics on the cumulative
trend of the number of defects/defect rate, which can be used to determine
whether the growth rate of defects is slowing down, showing a flat convergence
trend, and is an important reference for judging the stability of software
version quality<br/>
@@ -151,23 +151,23 @@ description: >
<tr>
<td>Incident Count</td>
<td>Number of Incidents found after shipping</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Bugs Count per 1k Lines of Code</td>
<td>Amount of bugs per 1,000 lines of code</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Incidents Count per 1k Lines of Code</td>
<td>Amount of incidents per 1,000 lines of code</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Delivery Cost</td>
<td>Commit Author Count</td>
<td>Number of Contributors who have committed code</td>
- <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
+ <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
<td>1. As a secondary indicator, this helps assess the labor cost of
participating in coding</td>
<td>1. Take inventory of project/team R&D resource inputs, assess
input-output ratio, and rationalize resource deployment</td>
</tr>
diff --git
a/versioned_docs/version-v0.12/DataModels/DevLakeDomainLayerSchema.md
b/versioned_docs/version-v0.12/DataModels/DevLakeDomainLayerSchema.md
index 8ad456a99a..770bbd6e8b 100644
--- a/versioned_docs/version-v0.12/DataModels/DevLakeDomainLayerSchema.md
+++ b/versioned_docs/version-v0.12/DataModels/DevLakeDomainLayerSchema.md
@@ -340,7 +340,7 @@ A pull request is the abstraction of Github pull request
and Gitlab merge reques
| `description` | longtext | | The body/description of pull
request
| |
| `status` | varchar | 255 | the status of pull requests.
For a Github pull request, the status can either be 'open' or 'closed'.
| |
| `parent_pr_id` | varchar | 255 | The id of the parent PR
| |
-| `pull_request_key` | varchar | 255 | The key of PR. Eg, 1536 is the
key of this [PR](https://github.com/merico-dev/lake/pull/1563)
| |
+| `pull_request_key` | varchar | 255 | The key of PR. Eg, 1536 is the
key of this [PR](https://github.com/apache/incubator-devlake/pull/1563)
| |
| `base_repo_id` | varchar | 255 | The repo that will be updated.
| |
| `head_reop_id` | varchar | 255 | The repo containing the changes
that will be added to the base. If the head repository is NULL, this means that
the corresponding project had been deleted when DevLake processed the pull
request.
| |
| `base_ref` | varchar | 255 | The branch name in the base
repo that will be updated
| |
diff --git a/versioned_docs/version-v0.12/EngineeringMetrics.md
b/versioned_docs/version-v0.12/EngineeringMetrics.md
index cdc0bc59ef..35805b293f 100644
--- a/versioned_docs/version-v0.12/EngineeringMetrics.md
+++ b/versioned_docs/version-v0.12/EngineeringMetrics.md
@@ -20,7 +20,7 @@ description: >
<td rowspan="10">Delivery Velocity</td>
<td>Requirement Count</td>
<td>Number of issues in type "Requirement"</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td rowspan="2">
1. Analyze the number of requirements and delivery rate of different time
cycles to find the stability and trend of the development process.
<br/>2. Analyze and compare the number of requirements delivered and delivery
rate of each project/team, and compare the scale of requirements of different
projects.
@@ -32,12 +32,12 @@ description: >
<tr>
<td>Requirement Delivery Rate</td>
<td>Ratio of delivered requirements to all requirements</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
</tr>
<tr>
<td>Requirement Lead Time</td>
<td>Lead time of issues with type "Requirement"</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td>
1. Analyze the trend of requirement lead time to observe if it has improved
over time.
<br/>2. Analyze and compare the requirement lead time of each project/team to
identify key projects with abnormal lead time.
@@ -48,7 +48,7 @@ description: >
<tr>
<td>Requirement Granularity</td>
<td>Number of story points associated with an issue</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td>
1. Analyze the story points/requirement lead time of requirements to evaluate
whether the ticket size, ie. requirement complexity is optimal.
<br/>2. Compare the estimated requirement granularity with the actual
situation and evaluate whether the difference is reasonable by combining more
microscopic workload metrics (e.g. lines of code/code equivalents)</td>
@@ -58,7 +58,7 @@ description: >
<tr>
<td>Commit Count</td>
<td>Number of Commits</td>
- <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
+ <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
<td>
1. Identify the main reasons for the unusual number of commits and the
possible impact on the number of commits through comparison
<br/>2. Evaluate whether the number of commits is reasonable in conjunction
with more microscopic workload metrics (e.g. lines of code/code
equivalents)</td>
@@ -68,7 +68,7 @@ description: >
<tr>
<td>Added Lines of Code</td>
<td>Accumulated number of added lines of code</td>
- <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
+ <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
<td rowspan="2">
1. From the project/team dimension, observe the accumulated change in Added
lines to assess the team activity and code growth rate
<br/>2. From version cycle dimension, observe the active time distribution of
code changes, and evaluate the effectiveness of project development model.
@@ -79,12 +79,12 @@ description: >
<tr>
<td>Deleted Lines of Code</td>
<td>Accumulated number of deleted lines of code</td>
- <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
+ <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
</tr>
<tr>
<td>Pull Request Review Time</td>
<td>Time from Pull/Merge created time until merged</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
<td>
1. Observe the mean and distribution of code review time from the
project/team/individual dimension to assess the rationality of the review
time</td>
<td>1. Take inventory of project/team code review resources to avoid
lack of resources and backlog of review sessions, resulting in long waiting time
@@ -93,7 +93,7 @@ description: >
<tr>
<td>Bug Age</td>
<td>Lead time of issues in type "Bug"</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td rowspan="2">
1. Observe the trend of bug age and locate the key reasons.<br/>
2. According to the severity level, type (business, functional
classification), affected module, source of bugs, count and observe the length
of bug and incident age.</td>
@@ -103,13 +103,13 @@ description: >
<tr>
<td>Incident Age</td>
<td>Lead time of issues in type "Incident"</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
</tr>
<tr>
<td rowspan="8">Delivery Quality</td>
<td>Pull Request Count</td>
<td>Number of Pull/Merge Requests</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
<td rowspan="3">
1. From the developer dimension, we evaluate the code quality of developers by
combining the task complexity with the metrics related to the number of review
passes and review rounds.<br/>
2. From the reviewer dimension, we observe the reviewer's review style by
taking into account the task complexity, the number of passes and the number of
review rounds.<br/>
@@ -121,24 +121,24 @@ description: >
<tr>
<td>Pull Request Pass Rate</td>
<td>Ratio of Pull/Merge Review requests to merged</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Pull Request Review Rounds</td>
<td>Number of cycles of commits followed by comments/final merge</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Pull Request Review Count</td>
<td>Number of Pull/Merge Reviewers</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
<td>1. As a secondary indicator, assess the cost of labor invested in
the code review process</td>
<td>1. Take inventory of project/team code review resources to avoid
long waits for review sessions due to insufficient resource input</td>
</tr>
<tr>
<td>Bug Count</td>
<td>Number of bugs found during testing</td>
- <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub
issues</a>, etc</td>
+ <td>Issue/Task Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/jira/README.md";>Jira
issues</a>, <a href="https://devlake.apache.org/docs/Plugins/github/";>GitHub
issues</a>, etc</td>
<td rowspan="4">
1. From the project or team dimension, observe the statistics on the total
number of defects, the distribution of the number of defects in each severity
level/type/owner, the cumulative trend of defects, and the change trend of the
defect rate in thousands of lines, etc.<br/>
2. From version cycle dimension, observe the statistics on the cumulative
trend of the number of defects/defect rate, which can be used to determine
whether the growth rate of defects is slowing down, showing a flat convergence
trend, and is an important reference for judging the stability of software
version quality<br/>
@@ -151,23 +151,23 @@ description: >
<tr>
<td>Incident Count</td>
<td>Number of Incidents found after shipping</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Bugs Count per 1k Lines of Code</td>
<td>Amount of bugs per 1,000 lines of code</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Incidents Count per 1k Lines of Code</td>
<td>Amount of incidents per 1,000 lines of code</td>
- <td>Source Code Management entities: <a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>
PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
+ <td>Source Code Management entities: <a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a> PRs, <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
MRs, etc</td>
</tr>
<tr>
<td>Delivery Cost</td>
<td>Commit Author Count</td>
<td>Number of Contributors who have committed code</td>
- <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://github.com/merico-dev/lake/blob/main/plugins/github/README.md";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
+ <td>Source Code Management entities: <a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitextractor/README.md";>Git</a>/<a
href="https://devlake.apache.org/docs/Plugins/github/";>GitHub</a>/<a
href="https://github.com/apache/incubator-devlake/blob/main/backend/plugins/gitlab/README.md";>GitLab</a>
commits</td>
<td>1. As a secondary indicator, this helps assess the labor cost of
participating in coding</td>
<td>1. Take inventory of project/team R&D resource inputs, assess
input-output ratio, and rationalize resource deployment</td>
</tr>
diff --git
a/versioned_docs/version-v0.13/DataModels/DevLakeDomainLayerSchema.md
b/versioned_docs/version-v0.13/DataModels/DevLakeDomainLayerSchema.md
index 49fdb5f182..f453002a83 100644
--- a/versioned_docs/version-v0.13/DataModels/DevLakeDomainLayerSchema.md
+++ b/versioned_docs/version-v0.13/DataModels/DevLakeDomainLayerSchema.md
@@ -356,7 +356,7 @@ A pull request is the abstraction of Github pull request
and Gitlab merge reques
| `description` | longtext | | The body/description of pull
request
| |
| `status` | varchar | 255 | the status of pull requests.
For a Github pull request, the status can either be 'open' or 'closed'.
| |
| `parent_pr_id` | varchar | 255 | The id of the parent PR
| |
-| `pull_request_key` | varchar | 255 | The key of PR. Eg, 1536 is the
key of this [PR](https://github.com/merico-dev/lake/pull/1563)
| |
+| `pull_request_key` | varchar | 255 | The key of PR. Eg, 1536 is the
key of this [PR](https://github.com/apache/incubator-devlake/pull/1563)
| |
| `base_repo_id` | varchar | 255 | The repo that will be updated.
| |
| `head_reop_id` | varchar | 255 | The repo containing the changes
that will be added to the base. If the head repository is NULL, this means that
the corresponding project had been deleted when DevLake processed the pull
request.
| |
| `base_ref` | varchar | 255 | The branch name in the base
repo that will be updated
| |
diff --git
a/versioned_docs/version-v0.15/DeveloperManuals/PluginImplementation.md
b/versioned_docs/version-v0.15/DeveloperManuals/PluginImplementation.md
index 38c08b494b..3af7aced19 100644
--- a/versioned_docs/version-v0.15/DeveloperManuals/PluginImplementation.md
+++ b/versioned_docs/version-v0.15/DeveloperManuals/PluginImplementation.md
@@ -35,7 +35,7 @@ A plugin mainly consists of a collection of subtasks that can
be executed by Dev
2.
[PluginInit](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_init.go)
allows a plugin to customize its initialization
3.
[PluginTask](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_task.go)
enables a plugin to prepare data prior to subtask execution
4.
[PluginApi](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_api.go)
lets a plugin exposes some self-defined APIs
-5.
[PluginMigration](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_migration.go)
is where a plugin manages its database migrations
+5.
[PluginMigration](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_migration.go)
is where a plugin manages its database migrations
6.
[PluginModel](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_model.go)
allows other plugins to get the model information of all database tables of
the current plugin through the GetTablesInfo() method. If you need to access
Domain Layer Models, please visit
[DomainLayerSchema](https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema/)
7.
[PluginBlueprint](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_blueprint.go)
is the foundation for Blueprint and Plugin to collaborate and generate a
reasonable Pipeline Plan based on User Settings. For example, a user may
declare that he/she wants to collect data from a GitHub Repo, which implies
that not only the issues and PRs, but also the git-meta-data including commits
history, branches, tags, etc. need to be collected. To do it and do it fast
[...]
diff --git a/versioned_docs/version-v0.15/Plugins/refdiff.md
b/versioned_docs/version-v0.15/Plugins/refdiff.md
index 539f1e2983..4836b91772 100644
--- a/versioned_docs/version-v0.15/Plugins/refdiff.md
+++ b/versioned_docs/version-v0.15/Plugins/refdiff.md
@@ -8,7 +8,7 @@ description: >
RefDiff is a plugin that performs calculation tasks and has 2 main purposes.
-- Calculate the difference in commits between releases/tags to [analyze the
amount of code in each
release](https://github.com/apache/incubator-devlake/blob/main/plugins/refdiff/tasks/commit_diff_calculator.go)
+- Calculate the difference in commits between releases/tags to [analyze the
amount of code in each
release](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/refdiff/tasks/commit_diff_calculator.go)
- Calculate the difference in commits between deployments to [calculate DORA
metrics](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/refdiff/tasks/deployment_commit_diff_calculator.go)
And the output of RefDiff is stored in the table commits_diffs,
finished_commits_diffs, ref_commits.
diff --git
a/versioned_docs/version-v0.16/DeveloperManuals/PluginImplementation.md
b/versioned_docs/version-v0.16/DeveloperManuals/PluginImplementation.md
index 38c08b494b..3af7aced19 100644
--- a/versioned_docs/version-v0.16/DeveloperManuals/PluginImplementation.md
+++ b/versioned_docs/version-v0.16/DeveloperManuals/PluginImplementation.md
@@ -35,7 +35,7 @@ A plugin mainly consists of a collection of subtasks that can
be executed by Dev
2.
[PluginInit](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_init.go)
allows a plugin to customize its initialization
3.
[PluginTask](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_task.go)
enables a plugin to prepare data prior to subtask execution
4.
[PluginApi](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_api.go)
lets a plugin exposes some self-defined APIs
-5.
[PluginMigration](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_migration.go)
is where a plugin manages its database migrations
+5.
[PluginMigration](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_migration.go)
is where a plugin manages its database migrations
6.
[PluginModel](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_model.go)
allows other plugins to get the model information of all database tables of
the current plugin through the GetTablesInfo() method. If you need to access
Domain Layer Models, please visit
[DomainLayerSchema](https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema/)
7.
[PluginBlueprint](https://github.com/apache/incubator-devlake/blob/main/backend/core/plugin/plugin_blueprint.go)
is the foundation for Blueprint and Plugin to collaborate and generate a
reasonable Pipeline Plan based on User Settings. For example, a user may
declare that he/she wants to collect data from a GitHub Repo, which implies
that not only the issues and PRs, but also the git-meta-data including commits
history, branches, tags, etc. need to be collected. To do it and do it fast
[...]
diff --git a/versioned_docs/version-v0.16/Plugins/refdiff.md
b/versioned_docs/version-v0.16/Plugins/refdiff.md
index 7c8b5d0b63..d4908c07d6 100644
--- a/versioned_docs/version-v0.16/Plugins/refdiff.md
+++ b/versioned_docs/version-v0.16/Plugins/refdiff.md
@@ -8,7 +8,7 @@ description: >
RefDiff is a plugin that performs calculation tasks and has 2 main purposes.
-- Calculate the difference in commits between releases/tags to [analyze the
amount of code in each
release](https://github.com/apache/incubator-devlake/blob/main/plugins/refdiff/tasks/commit_diff_calculator.go)
+- Calculate the difference in commits between releases/tags to [analyze the
amount of code in each
release](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/refdiff/tasks/commit_diff_calculator.go)
- Calculate the difference in commits between deployments to [calculate DORA
metrics](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/refdiff/tasks/deployment_commit_diff_calculator.go)
And the output of RefDiff is stored in the table commits_diffs,
finished_commits_diffs, ref_commits.
