Yes, We made a small tool to help developer review their PR. Seems a great supplement for Sweep AI.
Build your own PR review bot in 3 minutes here: https://github.com/flows-network/github-pr-summary
81–90 of 117 posts
Yes, We made a small tool to help developer review their PR. Seems a great supplement for Sweep AI.
Build your own PR review bot in 3 minutes here: https://github.com/flows-network/github-pr-summary
I'm wondering what will happen if we let ChatGPT review these PRs created by ChatGPT. Yes, We made a small tool to help developer review their PR. Seems a great supplement for Sweep AI. Build your own PR review bot in 3 minutes here: https://github.com/flows-network/github-pr-summary
So next up, we'll be hiring people to put the bugs into the code base, so AI companies like this can stay in business, right? No bugs means no AI to fix bugs.
Earlier quoted context omitted.
I just had it fix some outdated copy in a part of the UI. The nice thing is I didn't have to find the file myself, I just described what was wrong like I would a junior eng and let it find and fix it. Worked on the first try!
That's exactly the use case we want. We also let you specify the file path (ex: "main.py"). We noticed that Sweep's search works way better if there are comments, because the comments match up really well with the search queries (language language is easier than language code)
Similar to the prompt engineering for previous era GPT completion models.
How do you approach the problem of what files to look into to fix a bug? Just embeddings doesn't seem to cut it.
One thing we also do is match any files mentioned in the issue. So if you mention sweepai/api.py, we'll find that and add it to the fetched files. There's still more work to be done here, so look out for those!
Likely file name based scoring, and other rules + finetuned retrieval models (opt-in of course)
Earlier quoted context omitted.
That's exactly the use case we want. We also let you specify the file path (ex: "main.py"). We noticed that Sweep's search works way better if there are comments, because the comments match up really well with the search queries (language language is easier than language code)
May be rewriting user's description might help you match code better? Similar to the prompt engineering for previous era GPT completion models.
What is the Privacy Policy?
There's also an interesting discussion here about how it works: https://news.ycombinator.com/reply?id=36990160