Thanks for the feedback! Seems like the video is confusing to several people so I’ll work on improving it.
I can explain the first steps of the video here:
1. ykr git starts the TUI configured for git. This display a menu where each option is accessible via a keyboard shortcut.
2. User inputs “b”, which opens the “branch” menu.
3. User inputs “l” which runs the command to list all the branches and display them to the user. Hitting ctrl+r hides the result window.
4. Still in the branch menu, the user inputs “c” to create and switch to a new branch. This prompts them with a branch name and the user inputs “demo”. Submitting the branch name calls git checkout -b demo and display the results to the user.
The remaining steps show similar interactions to add and commit a file, as well as deleting a branch.
Does that help understanding how the UX works or are there still confusing parts?
I can explain the first steps of the video here:
1. ykr git starts the TUI configured for git. This display a menu where each option is accessible via a keyboard shortcut.
2. User inputs “b”, which opens the “branch” menu.
3. User inputs “l” which runs the command to list all the branches and display them to the user. Hitting ctrl+r hides the result window.
4. Still in the branch menu, the user inputs “c” to create and switch to a new branch. This prompts them with a branch name and the user inputs “demo”. Submitting the branch name calls git checkout -b demo and display the results to the user.
The remaining steps show similar interactions to add and commit a file, as well as deleting a branch.
Does that help understanding how the UX works or are there still confusing parts?