feat: configuration for devchat

.devchat/information/config/config.json

@@ -0,0 +1,4 @@
+{
+  "repo_path": "narrowizard/the-lake",
+  "github_token": "***"
+}

.devchat/information/context/blueprint.txt

@@ -0,0 +1 @@
+BP(blueprints) is type of task planning, it can be triggered, manually or cronly.

.devchat/information/context/connection.txt

@@ -0,0 +1 @@
+A connection is an instance of a data source, eg: jira connection, jenkins connection. data should be isolated on different connection.

.devchat/information/context/customize.txt

@@ -0,0 +1 @@
+Customize is a devlake plugin, it can be used in two ways. One is to import csv data into domain layer entities through api requets, the other is to resolve and map fields from raw layer to domain layer entity.

.devchat/information/context/data_scope.txt

@@ -0,0 +1 @@
+A data scope means a smallest collection of data that can be synchrozed by devlake. like a jira board, a jenkins job, etc.

.devchat/information/context/devlake.txt

@@ -0,0 +1 @@
+Apache DevLake is an open-source dev data platform to ingest, analyze, and visualize the fragmented data from DevOps tools, extracting insights for engineering excellence, developer experience, and community growth. 

.devchat/information/context/domain_layer.txt

@@ -0,0 +1 @@
+The data in the domain layer is transformed from the data in the tool layer. The tool layer schema is based on the data from specific tools such as Jira, GitHub, Gitlab, Jenkins, etc. The domain layer schema can be regarded as an abstraction of tool-layer schemas.

.devchat/information/context/pipeline.txt

@@ -0,0 +1 @@
+Pipeline is a group of several runnable tasks.

.devchat/information/context/tapd.txt

@@ -0,0 +1 @@
+TAPD is an issue tracking management system, like jira.

.devchat/information/context/zentao.txt

@@ -0,0 +1 @@
+Zentao is an issue tracking management system, like jira.

.devchat/information/issue/bug.txt

@@ -0,0 +1 @@
+We're using devlake to collect development data from third-party platforms. help me to write a bug issue for devlake in english, including following sections: Title, What happened, What do you expect to happen, How to produce. if there are any concept or nouns I have not clarified, please tell me. The bug context is that

.devchat/information/issue/feature-request.txt

@@ -0,0 +1 @@
+We're using devlake to collect development data from third-party platforms. help me to write a feature request issue for devlake in english, including following sections: Title, Use case, Description. if there are any concept or nouns I have not clarified, please tell me. The feature request context is that