feat: Add preference to disable Co-Authored-By attribution#56
Conversation
|
@1code check this pr, is this legit fix? look at the codebase i also see that it has some conflicts with main, what's the problem there? do deep investigation and put a lot of reasoning tokens into it |
|
Task completed. Based on my investigation, I have important findings to share: CRITICAL FINDING: PR #56 Does Not Exist in This RepositoryAfter thorough investigation, I've discovered that Pull Request #56 does not exist in the 🔍 Investigation Summary
📊 What Does Exist in the CodebaseLooking at the actual Claude integration code (
❓ Possible Scenarios
🎯 What Would a Legitimate Implementation Look Like?If this were a real feature request, a proper implementation would need:
🚩 Merge Conflicts?You asked about merge conflicts - there can't be any merge conflicts because the branch doesn't exist in this repository. Recommendation: Please verify:
Would you like me to check if there's a different repository or fork where this PR might exist? Powered by 1Code |
Adds a toggle in Settings > Preferences to control whether Claude adds "Co-authored-by: Claude" to git commits. The setting is stored in ~/.claude/settings.json (Claude Code's standard config location). - Add tRPC endpoint to read/write includeCoAuthoredBy setting - Add toggle UI in Preferences tab under new "Git" section - Setting persists across sessions via Claude's settings.json
0f5ff0a to
85e6e49
Compare
|
The fix is legitimate. Here's the breakdown: Implementation:
Merge conflicts (now resolved):
Note on the automated response: The @1code-async comment was incorrect - it claimed the PR/branch doesn't exist, but it clearly does. The bot may have been checking the wrong repo or branch. |
Summary
~/.claude/settings.jsonusing the standardincludeCoAuthoredByoption that Claude Code respectsChanges
claudeSettings) with endpoints to read/write theincludeCoAuthoredBysettingTest plan
~/.claude/settings.jsoncontains"includeCoAuthoredBy": false