[unclear] Module 2 leaves the delete code uncommitted, what should we do with it? #79
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
At the end of Module 2 the guide leaves the repo that we are in with an uncommitted cli.py file. Is that expected? Will it cause problems for later modules?
I just got to lab 3, and it wants worktree clean, which it isnt because of the cli.py from module 2 not being committed. we need to either add a commit to lab 2 or start lab three by committing that work or deleting it.
I just made it to module 4 and it looks like we ask the ai agent to add a delete by index command to the cli.py file again... so it sounds like we should not commit that last delete code, but we should probably revert it.