-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a restart whole tutorial button #476
Comments
I can see this as a problem with the online version where's it's not easy to open a new folder. So far it sounds like a "tutorial settings" may be helpful, something like how GitHub has repo settings. |
I am thinking to take up this issue. Here's what I think needs to be done.
Did I miss something else? |
Settings PageA settings page makes a lot of sense. There is definitely more functionality that could be added there. Resetting a TutorialThere is some existing logic for resetting to a commit in A step can contain more than one hash, so you'd have to take the last one. Also note that the reset events needs to be passed to the local vscode server (the code inside of src). The web portion does not have access to run on the file system. |
Yes. I found an already existing settings page. I've also reused the Reset button component if that's ok. |
Would there be a way to make it completely reset to the point where it's as if you just started a tutorial? Like empty out the workspace folder, and re-clone the repo or something? |
That's also possible. Deleting all files is a bit scary, maybe reset to the empty first commit, then run the init action again. |
Do we end up in a unclean state if we reset to level 1 step 1 and not use the other approaches above? |
So I have made a PR on based of the first solution which is reseting to level 1 step 1. I think that works fine and we can improve further on this base. |
I'm not sure if this is necessary, but it might be nice to have a button to restart a tutorial from the beginning. Opening an issue for discussion.
The text was updated successfully, but these errors were encountered: