You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
content: `${IDENTITY} Your mission is to create clean and comprehensive commit messages for two different changes in a single codebase and output them in the provided JSON format: one for a bug fix and another for a new feature.
219
+
{
220
+
role: 'system',
221
+
content: `${IDENTITY} Your mission is to create clean and comprehensive commit messages for two different changes in a single codebase and output them in the provided JSON format: one for a bug fix and another for a new feature.
220
222
221
223
Here are the specific requirements and conventions that should be strictly followed:
222
224
223
225
Commit Message Conventions:
224
226
- The commit message consists of three parts: Header, Body, and Footer.
content: `${IDENTITY} Your mission is to create clean and comprehensive commit messages in the given @commitlint convention and explain WHAT were the changes ${config.OCO_WHY ? 'and WHY the changes were done' : ''
266
-
}. I'll send you an output of 'git diff --staged' command, and you convert it into a commit message.
267
-
${config.OCO_EMOJI
268
-
? 'Use GitMoji convention to preface the commit.'
269
-
: 'Do not preface the commit with anything.'
270
-
}
271
-
${config.OCO_DESCRIPTION
272
-
? 'Add a short description of WHY the changes are done after the commit message. Don\'t start it with "This commit", just describe the changes.'
273
-
: "Don't add any descriptions to the commit, only commit message."
274
-
}
271
+
content: `${IDENTITY} Your mission is to create clean and comprehensive commit messages in the given @commitlint convention and explain WHAT were the changes ${
272
+
config.OCO_WHY ? 'and WHY the changes were done' : ''
273
+
}. I'll send you an output of 'git diff --staged' command, and you convert it into a commit message.
274
+
${
275
+
config.OCO_EMOJI
276
+
? 'Use GitMoji convention to preface the commit.'
277
+
: 'Do not preface the commit with anything.'
278
+
}
279
+
${
280
+
config.OCO_DESCRIPTION
281
+
? 'Add a short description of WHY the changes are done after the commit message. Don\'t start it with "This commit", just describe the changes.'
282
+
: "Don't add any descriptions to the commit, only commit message."
283
+
}
275
284
Use the present tense. Use ${language} to answer.
276
-
${config.OCO_ONE_LINE_COMMIT
277
-
? 'Craft a concise commit message that encapsulates all changes made, with an emphasis on the primary updates. If the modifications share a common theme or scope, mention it succinctly; otherwise, leave the scope out to maintain focus. The goal is to provide a clear and unified overview of the changes in a one single message, without diverging into a list of commit per file change.'
278
-
: ''
279
-
}
280
-
${config.OCO_OMIT_SCOPE
281
-
? 'Do not include a scope in the commit message format. Use the format: <type>: <subject>'
282
-
: ''
283
-
}
285
+
${
286
+
config.OCO_ONE_LINE_COMMIT
287
+
? 'Craft a concise commit message that encapsulates all changes made, with an emphasis on the primary updates. If the modifications share a common theme or scope, mention it succinctly; otherwise, leave the scope out to maintain focus. The goal is to provide a clear and unified overview of the changes in a one single message, without diverging into a list of commit per file change.'
288
+
: ''
289
+
}
290
+
${
291
+
config.OCO_OMIT_SCOPE
292
+
? 'Do not include a scope in the commit message format. Use the format: <type>: <subject>'
293
+
: ''
294
+
}
284
295
You will strictly follow the following conventions to generate the content of the commit message:
0 commit comments