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
Cursor currently supports generating git commit messages based on code changes. While this is a helpful feature, the automatically generated commit messages often do not align with specific commit conventions or formats used in different projects or organizations.
Feature Request
Provide a configuration option that allows users to define their preferred git commit format. This feature would enable teams to enforce consistency in commit messages and better integrate Cursor with their existing development workflows.
Proposed Solution
Introduce a configuration file (e.g., .cursor-config) or UI option where users can specify their desired commit format.
Support placeholders (e.g., {type}, {scope}, {description}) to structure the commit message, inspired by widely used conventions like Conventional Commits.
Allow users to define default values for placeholders or prompts for missing information during the commit generation process.
Provide a preview option for the generated commit message before finalizing it.
Background
Cursor currently supports generating git commit messages based on code changes. While this is a helpful feature, the automatically generated commit messages often do not align with specific commit conventions or formats used in different projects or organizations.
Feature Request
Provide a configuration option that allows users to define their preferred git commit format. This feature would enable teams to enforce consistency in commit messages and better integrate Cursor with their existing development workflows.
Proposed Solution
Example
A possible configuration might look like:
Related Issues
#2454
The text was updated successfully, but these errors were encountered: