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
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,8 +46,9 @@ Use Azure/OpenAI API to review Git changes, generate conventional commit message
46
46
1. Ensure that you have installed and enabled the "AI Commit" extension.
47
47
2. In VSCode settings, locate the "ai-commit" configuration options and configure them as needed.
48
48
3. Make changes in your project and add the changes to the staging area (git add).
49
-
4. Next to the commit message input box in the "Source Control" panel, click the "AI Commit" icon button. After clicking, the extension will generate a commit message and populate it in the input box.
50
-
5. Review the generated commit message, and if you are satisfied, proceed to commit your changes.
49
+
4. (Optional) If you want to provide additional context for the commit message, type it in the Source Control panel's message input box before clicking the AI Commit button.
50
+
5. Next to the commit message input box in the "Source Control" panel, click the "AI Commit" icon button. After clicking, the extension will generate a commit message (considering any additional context if provided) and populate it in the input box.
51
+
6. Review the generated commit message, and if you are satisfied, proceed to commit your changes.
51
52
52
53
> **Note**\
53
54
> If the code exceeds the maximum token length, consider adding it to the staging area in batches.
Copy file name to clipboardExpand all lines: src/prompts.ts
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -79,6 +79,10 @@ You will act as a git commit message generator. When receiving a git diff, you w
79
79
4. NO questions or comments
80
80
5. NO formatting instructions or metadata
81
81
82
+
## Additional Context
83
+
84
+
If provided, consider any additional context about the changes when generating the commit message. This context will be provided before the diff and should influence the final commit message while maintaining all other formatting rules.
0 commit comments