Fix CodeComments setting not passed

[EstebanDalelR]

Description

The data was not being passed, this properly responds with it

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Chore: cleanup/renaming, etc
• RFC
• Test

Notes

Acceptance

• I have read the Contributing guidelines
• I have read the Code of Conduct

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
watermelon	✅ Ready (Inspect)	Visit Preview	Jan 30, 2024 6:46pm

[watermelon-copilot-for-code-review]

Watermelon AI Summary

This Pull Request addresses a bug where a specific setting for CodeComments wasn't being correctly communicated within the system, and implements a fix to ensure that this setting is properly passed on as intended.

GitHub PRs

• #442 - Fix CodeComments setting not passed - By EstebanDalelR Just now

• #429 - Add new user page - By EstebanDalelR 1 weeks ago

• #62 - Chore/remove supporters section in readme - By baristaGeek 3 months ago

watermelon is an open repo and Watermelon will serve it for free.
🍉🫶

[baristaGeek]

Nice! It just commented this block of PII data 4 minutes ago