diff --git a/ts/00_commitinfo_data.ts b/ts/00_commitinfo_data.ts index 605d588..2baa4c8 100644 --- a/ts/00_commitinfo_data.ts +++ b/ts/00_commitinfo_data.ts @@ -3,6 +3,6 @@ */ export const commitinfo = { name: '@git.zone/tsdoc', - version: '1.1.36', + version: '1.1.37', description: 'An advanced TypeScript documentation tool using AI to generate and enhance documentation for TypeScript projects.' } diff --git a/ts/aidocs_classes/commit.ts b/ts/aidocs_classes/commit.ts index 34444ff..cc15c95 100644 --- a/ts/aidocs_classes/commit.ts +++ b/ts/aidocs_classes/commit.ts @@ -3,7 +3,8 @@ import { AiDoc } from '../classes.aidoc.js'; import { ProjectContext } from './projectcontext.js'; export interface INextCommitObject { - recommendedNextVersionLevel: 'patch' | 'minor' | 'major'; // the recommended next version level of the project + recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE'; // the recommended next version level of the project + recommendedScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names. recommendedNextVersion: string; // the recommended next version of the project message: string; // the commit message. use conventional commits format changelog?: string; // the changelog @@ -45,9 +46,10 @@ Your answer should be parseable with JSON.parse() without modifying anything. Here is the structure of the JSON you should return: { - recommendedNextVersionLevel: 'patch' | 'minor' | 'major'; // the recommended next version level of the project + recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE'; // the recommended next version level of the project + recommendedScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names. recommendedNextVersion: string; // the recommended next version of the project - message: string; // the commit message. use conventional commits format + message: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself. } You are being given the files of the project. You should use them to create the commit message.