Create a git branch named ”cursor” or something, maybe a feature branch.
Commit every time you’re moving forward with the composer/agent, my messages look like ”asdf” for a couple of hours
When you’re ready to merge to main branch, squash all the ”asdf” commits, maybe change commit message, then merge.
If you’re not used to do these things via the CLI, GutHub Desktop client is awesome.
This way, if you X hours later realize you’ve gone down the wrong path, you can just git reset --hard 0d1d7fc32 to a specific commit and start over.
I’m gonna create a VSCode extension for this flow if there isn’t already one. If I could press a keyboard shortcut that automatically commits everything in the working tree with message ”poop”, it would be nice.
If anyone have any other good workflows such as this, please share.
THIS. Yes please. Let me know if I can help. I have no idea why is not a default setting in cursor, given how much it likes to break features & delete parts of the project.
As you understand, for testing AI-proposed code changes, we HAVE to accept them.
As they may be across multiple files etc, it is hard to roll back if proper version control is not used.
So the natural solution is: make cursor use git without human supervision after each block of changes. My supervision should end with accepting changes. The grunt work of git mgmt should be done by cursor itself.
If out of all files proposed to update in a specific round of work, at least one is accepted, that should trigger a commit.