Thanks for hunting us @fmerian !
What is Watermelon?
For software engineering teams that spend a lot of time reviewing pull requests, we provide an open-source copilot for code review.
We trace the code context associated with PRs from sources like GitHub, Slack, Linear, and Notion. Our system identifies errors in PRs, initially focusing on console log detection and comments on the line diffs. Taking these insights into account, we conduct a pre-review of PRs and assign them appropriate labels.
Why us?@estebandalelr and I have been developing software for the past 6 years and we've worked at companies of all sizes, from 2-person to 1,000-person companies. Code review was always a pain for us.
Devs spend 30% of their time doing code reviews, and 40% of PRs don't contain a description. Despite advances in AI for code, there hasn't been much innovation around solving this pain point.
We aimed to create a tool that goes beyond just a basic syntactic analysis of the PR.
Please help us with the following. We will highly appreciate it:
- Introductions to engineering leaders at companies who use GitHub.
- Star us on GitHub.
- Install Watermelon and give us your feedback.
Thank you very much, ProductHunt! 😄
Congrats on the Watermelon launch! It's fantastic to see tools that streamline the code review process. I'm excited about the potential time-saving benefits for engineering teams. Keep up the great work!
@daxeelsoni thanks for your support! We’ve identified code review is a very common bottleneck for engineering teams, therefore we’re laser-focused on solving this.
May I ask, is your team’s bottleneck more around velocity or stability?
@matijash Thanks! Huge fan of Wasp BTW.
Long story short: First, it's different. All dev tools have a name mixing the word "Git", "Code", or "Source" with some other word. We're gonna win by being different.
Second, it has an emoji. Who doesn't like emojis? 🍉🍉🍉
This is a gamer changer. Commenting and reviewing pull requests is so time costuming. It's open source and streamlines the communication channel as well. Kudos founding team!
@yev_yev_yev Ty! Huge fan of Multiple here.
Not yet but it's something we're planning to expand into very soon as it's something that we can very easily do on top of what we have already built.
Can I ask, what language are you guys using?
We're using TypeScript. An example would be:
```typescript
const someFn = () => {
// const oldLeftoverVar = 10;
const x = 5;
return x;
}
```
I want to detect/remove the leftover code
Hey Esteban, I remember seeing watermelon long ago at the Pioneer tournament! It is great to see the project made a lot of progress and launched on ProductHunt. Congrats on the launch! I think it would be great if teams could add some rules for the PR. For example, if the PR size is too large, advise the developer to split the PR into multiple small PRs.
@atsuhiro_teshima Woah that was very long ago! We were not even building a dev tool back then. It's been so long in retrospect. Thanks for your support!
We've been thinking about adding something like this to our rules engine. For instance, we know that certain companies have a rule that says "a PR shouldn't exceed 200 LOC". What's going on around our heads is "how do we make this not so opinionated, but at the same time not so unopinionated as including the X number of LOC as a settings parameter?" "Is number of LOC the best proxy for everyone in the first place?"
Would you please give us some advice on this? How do you recommend we think about it?
@naveed_rehman there's a new breed of innovative tools adding AI to their products to expedite code review. That's correct.
Being open-source is key to differentiation. As developers, we prefer to install open stuff. We trust those products more. In addition to that, I want to give you a glimpse of something that's already having a test PR: We'll give you the ability to choose your model of preference if you're more inclined towards an OSS alternative to Open AI such as Mistral.
Beyond that and what's most important is that contrary to all these other products, we understand that we need to trace code context for LLMs to produce the best results.
This is so time-saving. Especially for those repositories who get tons of pull requests in a short amount of time. Great product guys and congrats on your launch.
@hosseinyazdi 100%. Repos with a lot of PRs are the ones that get the best use case. Very curious to learn: What is it exactly about the product that catches your attention the most?
Congrats on the launch! Watermelon's AI-assisted PR insights will help in streamlining the code collaboration, simplifying the PR reviews with smart tagging. It can become a game-changer for busy teams!
Watermelon