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?
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 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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.