Loading video...
Video Failed to Load
cursor pro tip for vibe coders: use the git tab to save changes and roll back quickly if the ai messes up seeing too many stories of vibe coders unable to get back to a working version 😰 watch the video
31,852 views • 1 year ago •via X (Twitter)
11 Comments

example of a situation where this could have been avoided

INTRODUCING: Agentic Security - LLM Security Scanner! 🔍 🔑 Features: Scans for prompt injections, jailbreaking & more. Provides detailed reports & options to customize attack rules. 🔗access the GitHub Link ↓

I just use 2 different branches. Main & Dev. All changes to dev. once m satisfied, i can merge to main (my production branch).

Cursor’s checkpointing works pretty well too to stay within the flow. Git usage assumes knowing which files to keep and not to keep… more robust but greater overhead

checkpoints will improve but right now if you’re not accepting changes until it gets things right it’s hard to scroll back and find the right one

I'm embarased to say that after 2 months learning cursor, i just found out about this. Thanks

we’re all learning every day!

I do this with the GitHub desktop app. It's not integrated with Cursor, but I find it much easier to understand what's going on. Especially if I'm working on multiple projects and have branches going.

.tsx ...where's .php? Are you a cool kid now?😂 j/k Great tip, btw. I always commit after each Cursor update.

haha i dabble in nextjs every now and then

git pushy...
