anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

Add configuration option to control commit/PR footer #405

New Issue
Closed
opened 2026-02-16 17:26:37 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:26:37 -05:00
Owner
Copy Link
Copy Source

Originally created by @allen-branch on GitHub (Jun 30, 2025).

Originally assigned to: @thdxr on GitHub.

Summary

Add a configuration option includeCoAuthoredBy to allow users to control whether the opencode footer is included in git commits and pull request descriptions, following the same pattern as Claude Code.

Background

Currently, opencode automatically adds this footer to all commit messages and PR descriptions:

🤖 Generated with [opencode](https://opencode.ai)

Co-Authored-By: opencode <noreply@opencode.ai>

User Demand

This was previously requested in #328 where a user noted:

"When doing a commit with opencode, it always adds the '🤖 Generated with [opencode]…' footer to the commit message, which I think implies that the code of this commit is generated and co-authored by AI, which doesn't have to be the case. I also like to use AI to just generate a commit message even when the code is written by hand."

A complete removal was attempted in PR #329 but this approach removes the footer for all users. A configuration option provides better flexibility.

Proposed Solution

Add an includeCoAuthoredBy boolean configuration option that:

  • Defaults to true (maintains current behavior, no breaking changes)
  • Follows Claude Code's exact naming convention for familiarity
  • Controls footer inclusion in both commits and PRs
  • Is configurable via opencode.json

Configuration Example

{
  "includeCoAuthoredBy": false
}

Benefits

  • Backward compatible - existing users see no change
  • Industry standard - matches Claude Code's approach exactly
  • User choice - allows customization based on use case
  • Clear naming - self-documenting configuration

Implementation

The implementation requires:

  1. Add includeCoAuthoredBy boolean to config schema (default: true)
  2. Modify bash tool to conditionally include footer based on config
  3. Update documentation

Estimated effort: 30-45 minutes

References

This addresses a documented user need while maintaining compatibility and following established patterns in the AI coding tool ecosystem.

Originally created by @allen-branch on GitHub (Jun 30, 2025). Originally assigned to: @thdxr on GitHub. ## Summary Add a configuration option `includeCoAuthoredBy` to allow users to control whether the opencode footer is included in git commits and pull request descriptions, following the same pattern as Claude Code. ## Background Currently, opencode automatically adds this footer to all commit messages and PR descriptions: ``` 🤖 Generated with [opencode](https://opencode.ai) Co-Authored-By: opencode <noreply@opencode.ai> ``` ## User Demand This was previously requested in #328 where a user noted: > "When doing a commit with opencode, it always adds the '🤖 Generated with [opencode]…' footer to the commit message, which I think implies that the code of this commit is generated and co-authored by AI, which doesn't have to be the case. I also like to use AI to just generate a commit message even when the code is written by hand." A complete removal was attempted in PR #329 but this approach removes the footer for all users. A configuration option provides better flexibility. ## Proposed Solution Add an `includeCoAuthoredBy` boolean configuration option that: - **Defaults to `true`** (maintains current behavior, no breaking changes) - **Follows Claude Code's exact naming convention** for familiarity - **Controls footer inclusion in both commits and PRs** - **Is configurable via `opencode.json`** ### Configuration Example ```json { "includeCoAuthoredBy": false } ``` ### Benefits - **Backward compatible** - existing users see no change - **Industry standard** - matches Claude Code's approach exactly - **User choice** - allows customization based on use case - **Clear naming** - self-documenting configuration ## Implementation The implementation requires: 1. Add `includeCoAuthoredBy` boolean to config schema (default: `true`) 2. Modify bash tool to conditionally include footer based on config 3. Update documentation Estimated effort: 30-45 minutes ## References - Claude Code documentation: https://docs.anthropic.com/en/docs/claude-code/settings#available-settings - Related issue: #328 - Previous attempt: #329 This addresses a documented user need while maintaining compatibility and following established patterns in the AI coding tool ecosystem.
yindo closed this issue 2026-02-16 17:26:37 -05:00
yindo commented 2026-02-16 17:26:37 -05:00
Author
Owner
Copy Link
Copy Source

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#405
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?