Yeah, true. Going to be interesting to find the right balance of what feedback should open a ticket at all :)

4. PR gets merged
5. Linear closes ticket automatically
6. Feedbackview notifies customer autoamtically

The automation rules would let users define what should actually auto-create a ticket, eg. only bugs that have a high impact score.

linear.app/changelog/20...

Oh yeah, Linear and GitHub integrations are definitely coming! Trying to grasp what makes most sense to build first at the moment.

It could work like this:
1. Feedback received in Feedbackview
2. Automation rule creates Linear issue automatically
3. Linear hands off to GitHub Co-pilot automatically

Thanks Veni! 🙌

True – gotta tripe check all the things, but still much faster!

AI is definitely a force multiplier these days for me, especially when working solo on a project. Still took a good 2 months for me, working on it on the side. Bet Val spent a good amount of time on the new thing too!

No pressure! :D

Not sure if you're into AI IDEs, but if you're using Windsurf, they have an option that lets you reference all the code etc. when you turn "write mode" on, but it can't do any edits. Pretty useful if you want to reason about something without the actual implementation.

Claude 3.7 💯

That sounds unpleasant. You should totally do that :D

Ah that’s even harder to prevent then, oof :-/

It’s like grocery shopping with a toddler. You let them roam and it works okay and the second you become complacent they trash the entire aisle. Always keep an eye on the toddlers 😄

Adds friction, but you could require account activation through email on signup. Would only do if this is a big issue

I always had one Paddle account per product and they were tranferred fully when selling.