allisonee

5 ms·

1. 1.▲
   by allisonee 1y ago

   Ultimately, the author (the engineer writing the PR) should always fully own the impact and consequences of their code. This has always been true, but it’s become even more critical with AI-assisted coding and more junior engineers who prim
2. 2.▲
   by allisonee 1y ago

   Glad to hear the product resonates! Hope your team likes it, and please share any feedback as you try it out. If helpful, I can also start a direct slack channel between our teams, just reach out to contact@mrge.io with your slack emails!
3. 3.▲
   by allisonee 1y ago

   we're in the process of getting our soc2 approved, stay tuned!
4. 4.▲
   by allisonee 1y ago

   thanks for the feedback and glad to hear that parts of our platform resonate. let me know if we can help onboard the team in the future if that makes it easier, it should be quick to switch as we also have our own cli. right now, our bill
5. 5.▲
   by allisonee 1y ago

   on our roadmap! please reach out at contact@mrge.io if you want to get notified on launch :)
6. 6.▲
   by allisonee 1y ago

   glad to see this resonates - seems like many of us are experiencing the same challenges with AI codegen!
7. 7.▲
   by allisonee 1y ago

   thanks for bringing this up! we're currently free (unlimited PRs) and will soon bill $20-$30/active user (has committed a PR) per month. We'll try to make this clearer!
8. 8.▲
   by allisonee 1y ago

   totally get where you're coming from--many big open source repos have also been using it for a while and have seen some FP but have generally felt that the quality overall was worth it. would love to continue having you try it out, bu
9. 9.▲
   by allisonee 1y ago

   thanks for bringing this up, and totally understand the concern. we are committed to security, and we never write/access your code without your action--the only reason that setting is necessary is so that you can merge/1-click co
10. 10.▲
    by allisonee 1y ago

    sorry to hear that it didn't catch all the issues! if you downvote/upvote or reply directly to the bot comment @mrge-io <feedback>, we can improve it for your team. We take all these into consideration when improving our AI,
11. 11.▲
    by allisonee 1y ago

    just to follow up--the fix for this is landing! thanks for surfacing
12. 12.▲
    by allisonee 1y ago

    thanks for the feedback! Glad that our ai reviewer has been useful to your team!
13. 13.▲
    by allisonee 1y ago

    sorry about that! we're looking into this now--if you go back to https://github.com/apps/mrge-io-dev/installations/select_tar... and just add repos you want to use us with under the "select reposito
14. 14.▲
    by allisonee 1y ago

    appreciate the honest reaction! We'll think about this more, what we were trying to get at is that cursor is more about code writing, and we're tackling the review/collaboration side :) curious if anything else would have imm
15. 15.▲
    by allisonee 1y ago

    On the roadmap! If you're happy to share your email for an early link when we do support it, send to contact@mrge.io
16. 16.▲
    by allisonee 1y ago

    thanks Tim! So glad it's been helping your team move faster
17. 17.▲
    by allisonee 1y ago

    that makes total sense, thanks for the feedback! we debated this for a bit--will keep in mind for the next design pass on the site :)
18. 18.▲
    by allisonee 1y ago

    good q! today, we'd clone the whole thing, but we're actively looking into solutions about that atm (ie: only cloning the relevant subdirs) for custom rules, we do handle large monorepos by allowing you to add an allowlist (or exc
19. 19.▲
    by allisonee 1y ago

    that's a good question! today, we don't look at previous commits--but thats something that we'll consider for future roadmap. curious if this happens often to your team? and if so, how you general gauge "better" (o
20. 20.▲
    by allisonee 1y ago

    We had heard the same from a few early users, but they've commented that our AI is a more context aware/useful. Of course, that's just anecdotal. We'd love to give you a free trial ( https://mrge.io/invit
21. 21.▲
    by allisonee 1y ago

    Appreciate the feedback! We currently auto-suggest custom rules based on your comment history (and .cursorrules), however continuing to suggest from history is now on the roadmap thanks to your suggestion! On working with Devin: Yes, right
22. 22.▲
    by allisonee 1y ago

    good question! we currently support a direct integration with github via a github app. we'll make that clearer in the post.
23. 23.▲
    by allisonee 1y ago

    congrats on the launch! excited to try it out!