ishangsf/DeepCodeGeniusWeb-vscode
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update devchat

Browse Source
This commit is contained in:
bobo.yang 2023-05-11 13:55:16 +08:00
parent 1d48df44a4
commit 537626b3c8
3 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
package.json
View File

@ -4,6 +4,7 @@
"description": "devchat", "description": "devchat",
"version": "0.0.27", "version": "0.0.27",
"icon": "assets/devchat.png", "icon": "assets/devchat.png",
"publisher": "merico",
"engines": { "engines": {
"vscode": "^1.77.0" "vscode": "^1.77.0"
}, },

3
src/toolwrapper/devchat.ts
View File

@ -273,8 +273,7 @@ class DevChat {
return []; return [];
} }
const stdoutNew = "[" + stdout.replace(/\}\n\]\n\[\n \{\n/g, "}\n],\n[\n {\n") + "]"; return JSON.parse(stdout.trim());
return JSON.parse(stdoutNew.trim());
} catch (error) { } catch (error) {
logger.channel()?.error(`Error getting log: ${error}`); logger.channel()?.error(`Error getting log: ${error}`);
logger.channel()?.show(); logger.channel()?.show();

8
workflows/commit_message/instruct.txt
View File

@ -2,7 +2,13 @@ As a software developer assistant, your task is to provide clear and concise res
1. A commit message should include a title and multiple body lines. 1. A commit message should include a title and multiple body lines.
2. Adhere to best practices, such as keeping titles under 50 characters and limiting body lines to under 72 characters. 2. Adhere to best practices, such as keeping titles under 50 characters and limiting body lines to under 72 characters.
3. Enclose messages in code blocks using triple backticks (```), and flag code type as commitmsg. 3. Format all commit messages by enclosing each message within a block of triple backticks (```), and include 'commitmsg' alongside the beginning backticks. For example:
```commitmsg
The title
- The first line.
- The second line.
```
4. Utilize the <context>, if provided, to create the summary. 4. Utilize the <context>, if provided, to create the summary.
5. Utilize the previous messages, if provided in the end of this prompt, to create the summary. Note that not all previous messages are necessarily relevant. 5. Utilize the previous messages, if provided in the end of this prompt, to create the summary. Note that not all previous messages are necessarily relevant.