feat: make commit signature configurable #8149
Closed
+229
−36
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add disableCommitSignature config option to allow users to disable the automatic inclusion of Continue attribution in commit messages. - Add disableCommitSignature to config interfaces - Update system message to conditionally include signature - Add comprehensive tests for the new behavior - Update documentation in config.yaml reference Generated with [Continue](https://continue.dev) Co-Authored-By: Continue <noreply@continue.dev>
dosubot
bot
added
the
size:M
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Generated with [Continue](https://continue.dev) Co-Authored-By: Continue <noreply@continue.dev>
Generated with [Continue](https://continue.dev) Co-Authored-By: Continue <noreply@continue.dev>
The disableCommitSignature property was added to the AssistantUnrolled schema but the package build was failing due to missing @continuedev/config-types dependency. Installed the dependency and rebuilt the package to update TypeScript types. Generated with [Continue](https://continue.dev) Co-Authored-By: Continue <noreply@continue.dev>
Generated with [Continue](https://continue.dev) Co-Authored-By: Continue <noreply@continue.dev>
RomneyDa
requested changes
Oct 9, 2025
Collaborator
RomneyDa
left a comment
RomneyDa
left a comment
There was a problem hiding this comment.
Requesting changes to delay merging as we don't currently top level settings like this to config yaml
Collaborator
|
@rossigee currently settings like this live in |
* Add notion cookbook * Add notion draft * Add draft notion cookbook * Update docs/guides/notion-continue-cookbook.mdx Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> * Change cookbook to guide using API since MCP doesn't work * Move out of MCP cookbooks in overview * Apply suggestion from @cubic-dev-ai[bot] Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> --------- Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> Co-authored-by: Brian Douglas <bdougie@users.noreply.github.com>
- Added dismissable banner to docs.json - Banner promotes CLI v1.4.49 release and links to MCP Cookbooks - Banner is dismissable for better UX Generated with [Continue](https://continue.dev) Co-Authored-By: Continue <noreply@continue.dev> Co-authored-by: Username <bekah@continue.dev>
This reverts commit a6daeb8.
- Move disableCommitSignature from config.yaml to GlobalContext for user preferences - Add /set slash command for configuring CLI preferences - Update documentation to reflect new user-configurable setting - Add comprehensive tests for the new functionality - Maintain backward compatibility with default attribution enabled The setting is now stored in GlobalContext and can be configured using: - /set disableCommitSignature true (disable attribution) - /set disableCommitSignature false (enable attribution, default)
dosubot
bot
added
size:XXL
dosubot
bot
added
size:L
Collaborator
…ossigee/feature/disable-commit-signature-config
RomneyDa
requested changes
Oct 27, 2025
Collaborator
RomneyDa
left a comment
RomneyDa
left a comment
There was a problem hiding this comment.
@rossigee went over this with @TyDunn again today, sorry for the back and forth but we're thinking the slash command doesn't quite feel right. We could build a TUI menu where users could easily toggle but it doesn't solve CICD scenarios and the global context is a bit saturated (I know I requested putting it there).
We're thinking let's rip out the persisted setting altogether and just use an environment variable like CONTINUE_CLI_DISABLE_COMMIT_SIGNATURE. Thoughts on this?
Contributor
Author
|
That's a much better, simpler approach. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added a new configuration option
disableCommitSignatureto allow users to disable the automatic inclusion of Continue attribution in commit messages generated by the CLI. This makes the signature configurable for users who prefer not to include it.Key changes:
disableCommitSignatureboolean optionAI Code Review
@continue-reviewChecklist
Screen recording or screenshot
[Not applicable for this configuration change.]
Tests
Added tests in
extensions/cli/src/systemMessage.test.tsto verify the signature is included or excluded based on thedisableCommitSignatureconfig option.Summary by cubic
Made the Continue commit attribution optional for CLI-generated commits via a new disableCommitSignature config. By default the signature is included; set disableCommitSignature: true to remove it.
New Features
Migration