Allow empty responses

[EstebanDalelR]

Description

When the commit list is empty, it gave a 500. This is a case of a new repo, we should handle gracefully.

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

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	Comments	Updated (UTC)
watermelon	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 28, 2023 3:40pm

[watermelon-copilot-for-code-review]

WatermelonAI Summary

The commit and the PR in question are about allowing empty responses in a specific case where the commit list is empty. Previously, this would cause a 500 error, but now it is handled gracefully. This is a bug fix and it aligns with the goal of improving user experience by preventing errors in a scenario that can occur with a new repository.

GitHub PRs

• #317 - Allow empty responses

• #44 - Add test hover

• #7 - Feature/hover

• #15 - Update README.md

• #312 - Feature/intellijdownload

Click here to login to Jira
Click here to login to Confluence
Slack Threads deactivated by EstebanDalelR

Notion Pages

• #undefined - Fix stacking of elements in the extension

• #undefined - Create the /api/subscriptions/addEmails endpoint

Linear Tickets deactivated by EstebanDalelR
Click here to login to Asana
watermelon is an open repo and Watermelon will serve it for free.
🍉🫶

[baristaGeek]

Is the mentioned 500 behavior only happening with Slack in the scenario of an empty commit list?

[EstebanDalelR]

Is the mentioned 500 behavior only happening with Slack in the scenario of an empty commit list?

AFAIK, yes, tested a couple times and only slack breaks, so I guess this kills the error.