Update version and configuration settings (#3)
### Modifications - Updated `VERSION` file from `0.0.5` to `0.0.6`. - Modified `ait.commit.sample.config.json`: - Adjusted `temperature` from 0.7 to 0.6. - Modified `ait.pull_request.sample.config.json`: - Revised the prompt to exclude closing statements. - Increased `max_tokens` from 1000 to 2000. - Adjusted `temperature` from 0.7 to 0.6. ### Description This pull request includes updates to the version number and configuration settings for the commit and pull request message generator: 1. **Version Update**: - The version number in the `VERSION` file has been incremented from `0.0.5` to `0.0.6`. 2. **Commit Sample Config Adjustments**: - The `temperature` setting in `ait.commit.sample.config.json` has been lowered from 0.7 to 0.6 to refine the output generation. 3. **Pull Request Sample Config Enhancements**: - The prompt in `ait.pull_request.sample.config.json` was updated to exclude any closing statements or generic sentences. - The `max_tokens` parameter was increased from 1000 to 2000 to allow for more detailed output. - The `temperature` setting was also adjusted from 0.7 to 0.6 for consistent behavior across configurations.
This commit is contained in:
@@ -6,5 +6,5 @@
|
|||||||
"prompt": "Generate a concise commit message based on the provided Git diffs, including:\\n - A short and direct subject line (under 50 characters) summarizing the specific changes. No formatting should be used in the subject line.\\n - A brief bullet-point list of the exact modifications made, with basic Markdown formatting allowed in the body.\\n \\n Focus strictly on the changes themselves, avoiding any speculation about the reasons or potential impacts. Ensure that the message is informative enough to understand the changes without needing additional context.",
|
"prompt": "Generate a concise commit message based on the provided Git diffs, including:\\n - A short and direct subject line (under 50 characters) summarizing the specific changes. No formatting should be used in the subject line.\\n - A brief bullet-point list of the exact modifications made, with basic Markdown formatting allowed in the body.\\n \\n Focus strictly on the changes themselves, avoiding any speculation about the reasons or potential impacts. Ensure that the message is informative enough to understand the changes without needing additional context.",
|
||||||
"model": "gpt-4o",
|
"model": "gpt-4o",
|
||||||
"max_tokens": 1000,
|
"max_tokens": 1000,
|
||||||
"temperature": 0.7
|
"temperature": 0.6
|
||||||
}
|
}
|
@@ -3,8 +3,8 @@
|
|||||||
"diff_expression": "main...",
|
"diff_expression": "main...",
|
||||||
"log_expression": "main...",
|
"log_expression": "main...",
|
||||||
"system_prompt": "**You are an automatic pull request message generator and an expert in this field!**",
|
"system_prompt": "**You are an automatic pull request message generator and an expert in this field!**",
|
||||||
"prompt": "Generate a concise pull request message based on the provided Git diffs, including:\\n - A short and direct subject line (under 50 characters) summarizing the specific changes. No formatting should be used in the subject line.\\n - A brief bullet-point list of the exact modifications made, with basic Markdown formatting allowed in the body.\\n - A detailed description in Markdown format explaining the changes, their purpose, and any additional context that is relevant for the reviewers.\\n \\n Focus strictly on the changes themselves, avoiding any speculation about the reasons or potential impacts beyond the modifications. Ensure that the message is informative enough to understand the changes and their context for a comprehensive review.",
|
"prompt": "Generate a concise pull request message based on the provided Git diffs, including:\\n - A short and direct subject line (under 50 characters) summarizing the specific changes. No formatting should be used in the subject line.\\n - A brief bullet-point list of the exact modifications made, with basic Markdown formatting allowed in the body.\\n - A detailed description in Markdown format explaining the changes, and any additional context that is relevant for the reviewers.\\n \\n Focus strictly on the changes themselves, avoiding any speculation about the reasons or potential impacts.\\n **Do not include any closing statements or generic sentences. End the message immediately after providing the necessary details.**",
|
||||||
"model": "gpt-4o",
|
"model": "gpt-4o",
|
||||||
"max_tokens": 1000,
|
"max_tokens": 2000,
|
||||||
"temperature": 0.7
|
"temperature": 0.6
|
||||||
}
|
}
|
Reference in New Issue
Block a user