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

Feature/watermelon as reviewer 0#282

Merged
baristaGeek merged 19 commits intodevfrom
feature/Watermelon-as-reviewer-0
Sep 14, 2023
Merged

Feature/watermelon as reviewer 0#282
baristaGeek merged 19 commits intodevfrom
feature/Watermelon-as-reviewer-0

Conversation

@baristaGeek
Copy link
Collaborator

Description

This PR adds the "Watermelon as Reviewer 0" feature: We compare the title of the PR with the Watermelon AI summary, score how similar those 2 are, and based on that rating label a PR if it's safe to merge.

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

Acceptance

@vercel
Copy link

vercel bot commented Sep 5, 2023

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 14, 2023 8:26pm

Copy link
Member

@EstebanDalelR EstebanDalelR left a comment

Choose a reason for hiding this comment

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

I would rather it happened on the action, instead of on the extension

@baristaGeek
Copy link
Collaborator Author

I would rather it happened on the action, instead of on the extension

Ah! It seems like I had a conceptual vacuum about this. Thanks.

Basically, I thought that extension/getContext served both UIs. I'll fix it.

@watermelon-copilot-for-code-review
Copy link

watermelon-copilot-for-code-review bot commented Sep 7, 2023

WatermelonAI Summary

The 19 commits in the Pull Request indicate a series of changes related to the feature of having Watermelon as a reviewer. These changes include building a prompt to produce desired results, flagging PRs, changing comparison strings for detecting already labeled PRs, updating hardcoded PR titles and numbers to those stored on GitHub, removing console logs, fixing parameter names, and moving logic to a separate file. These commits also involve removing unnecessary code, refactoring to prevent race conditions, adding error handling, and tracking PR ratings per repo on PostHog. Overall, these changes aim to improve the functionality and reliability of Watermelon as a reviewer. Additionally, the PR title suggests that this Pull Request attempts to standardize API responses for easier processing and storage.

GitHub PRs

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

Notion Pages

Linear Tickets deactivated by EstebanDalelR
Click here to login to Asana
Your team WatermelonTools has used Watermelon 704 times.

…el removing if after syncrhonyzation the PR doesnt meet the business requirements
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