-
Notifications
You must be signed in to change notification settings - Fork 4.1k
feat: cli commit signature #7620
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No issues found across 1 file
|
💡 To request a new review, comment |
bdougie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should get that noreply@continue.dev email set up @sestinj. I'd love to see if we installs and cn sessions increase this month from a little exposire.
|
🎉 This PR is included in version 1.13.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Description
Adds instructions to include a commit signature when making commits not in plan mode:
Other example candidates to commit signature
Generated with cn
Generated with cn
Generated with Continue CLI
Generated with Continue CLI
Can make this configurable in the future
We could also put this in the terminal tool explicitely but then it wouldn't be included when using e.g. gh or git mcp, maybe better to just instruct it
Summary by cubic
Add a commitSignature context to the CLI system message for non-plan modes, instructing commits to include "Generated with Continue" and "Co-Authored-By: Continue noreply@continue.dev". This standardizes attribution for generated commits while leaving plan mode unchanged.