feat: add information for dev chat

apache#7090

.devchat/information/config/config.json

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

.devchat/information/context/devchat.txt

@@ -0,0 +1 @@
+DevChat is an open-source platform that empowers developers to leverage AI for code generation and documentation.

.devchat/information/issue/bug.txt

@@ -1 +1,38 @@
-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
+We're using devlake to collect development data from third-party platforms. help me to write a bug issue for devlake in english, here is an example bug issue title: "[Bug][Zentao] 500 Internal Server Error When Calling 'projects' API on ZenTao 18.10 Integration", here is the body of an example bug issue:
+### Search before asking
+
+- [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar issues.
+
+
+### What happened
+
+When integrating Apache DevLake with ZenTao version 18.10, the API endpoint 'projects' is returning a 500 Internal Server Error. Examination of the logs indicates that there's a failure in parsing the response from the ZenTao 'projects' API.
+
+### What do you expect to happen
+
+The expected behavior is that the 'projects' API call should successfully return a list of projects without any errors. Apache DevLake should be able to parse the response and integrate the data from ZenTao 18.10 for further analysis and visualization.
+
+### How to reproduce
+
+Set up Apache DevLake and configure it for integration with a ZenTao 18.10 instance.
+Authenticate as necessary to ensure communication with ZenTao's APIs.
+Trigger the 'projects' API call to fetch the list of projects from the ZenTao instance.
+Observe that the API response results in a 500 Internal Server Error, and check the logs to confirm that parsing the response is where the failure occurs.
+
+### Anything else
+
+The content in logs contain sensitive data, To get the log, pls contact me!
+
+### Version
+
+release-v0.20
+
+### Are you willing to submit PR?
+
+- [ ] Yes I am willing to submit a PR!
+
+### Code of Conduct
+
+- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
+
+The bug context is that

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

@@ -1 +1,33 @@
-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
+We're using devlake to collect development data from third-party platforms. help me to write a feature request issue for devlake in english, here is an example feature request issue title: [Feature][Dashboard] Re-organize dashboards, here is the body of an example feature request issue:
+### Search before asking
+
+- [X] I had searched in the [issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and found no similar feature requirement.
+
+
+### Use case
+
+This feature impacts the users of the DevLake platform who utilizes Jira as a third-party tool for tracking development tasks. Notably, the developers and project managers who frequently use Jira to manage their software development tasks would benefit from a preemptive alert on the changes in filter queries, enabling them to avoid the confusion, loss of time, and data incongruence.
+
+### Description
+
+It is currently observed that during the synchronization of Jira boards, the filter query pertinent to the sync is not stored for comparison. This has generated scenarios where there are unnoticed alterations in the filter query, which result in data inconsistencies and costly full-data synchronization to overwrite the dirtied data.
+
+This feature requests the saving of the intended filter query for syncing before the commencement of the Jira board synchronization. It would serve a dual purpose:
+
+Locally store the data of the filter queries for future reference.
+Monitor any alterations in the filter queries. If any changes are detected from the previous synchronization, an error alert should be triggered to warn the user before data synchronization.
+In most instances, alterations in filter queries require comprehensive synchronization to overwrite incorrect or false data. By implementing this feature, the platform will ensure more reliable data transfer, enhance user experience due to fewer inconsistencies, and result in saving time and resources by avoiding unnecessary data overwriting operations.
+
+### Related issues
+
+_No response_
+
+### Are you willing to submit a PR?
+
+- [ ] Yes I am willing to submit a PR!
+
+### Code of Conduct
+
+- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
+
+The feature request context is that