Skip to content
This repository has been archived by the owner on Mar 12, 2024. It is now read-only.

Fix CodeComments setting not passed #442

Merged
merged 1 commit into from
Feb 1, 2024
Merged

Fix CodeComments setting not passed #442

merged 1 commit into from
Feb 1, 2024

Conversation

EstebanDalelR
Copy link
Member

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

Copy link

vercel bot commented Jan 30, 2024

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 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

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

Copy link
Collaborator

@baristaGeek baristaGeek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Screenshot 2024-02-01 at 3 39 44 PM

@baristaGeek baristaGeek merged commit ac9b0de into dev Feb 1, 2024
3 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants