You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Show every single command being run in the terminal for user confirmation.
Potential solution: add the git command(s) under the instructions and above the header text.
E.g. :
`git branch -d` will be run for each branch you delete.
You have user confirmation already, right? I think you should place them during the "Confirm deleting branches? [Yes] [No]" prompt, and all similar prompts.
I basically want you to wrap your run_git_command() function or something, and have it prompt the user by default every time a command is run.
Maybe commands that are read-only would instead tell the user after the fact. For example just saying git branch or git diff doesn't need confirmation. But git push or git switch could, because they do something.
You'd want a bit of user testing to figure out which commands are good for prompting or for informing after the fact.
The text was updated successfully, but these errors were encountered:
Show every single command being run in the terminal for user confirmation.
Potential solution: add the git command(s) under the instructions and above the header text.
E.g. :
Original idea is from -Redstoneboi-:
Reddit comments: https://www.reddit.com/r/rust/comments/19bauiq/media_introducing_r3bl_giti_an_interactive_git/kj455u8/?context=8&depth=9
You have user confirmation already, right? I think you should place them during the "Confirm deleting branches? [Yes] [No]" prompt, and all similar prompts.
I basically want you to wrap your run_git_command() function or something, and have it prompt the user by default every time a command is run.
Maybe commands that are read-only would instead tell the user after the fact. For example just saying git branch or git diff doesn't need confirmation. But git push or git switch could, because they do something.
You'd want a bit of user testing to figure out which commands are good for prompting or for informing after the fact.
The text was updated successfully, but these errors were encountered: