Hacker News new | ask | show | jobs
by sunnybeetroot 392 days ago
Why commit halfway through implementing something with Cursor? Can you not wait until it’s created a feature or task that has been validated and tests written for it?
2 comments

Why wait until everything is finalized before committing? Git is distributed/local, so while one philosophy is to interact with it as little as possible, the other one is to commit early and commit often, and easily be able to rollback to a previous (working) state, with the caveat that you clean-up history before firing off a PR.
Why not create a branch and rollback only what needs to be rolled back? Branches are O(1) with git, right?
OP was insinuating that rolling back commits is a pain point.
Well, same statement applies. Rolling back commits is also O(1) and just as easy. And if you branch to start with it's not even a "rollback" through the commit history, it's just a branch switch. Feel like OP has never used git before or something.
Which seems like a tooling issue, imo. In Aider, it's just /undo.