Lazygit should be tested in a disposable repository with the operations your team performs most: stage individual hunks, amend a commit, resolve a conflict, inspect a branch, and recover from a mistaken action. Watch the underlying Git state after each step rather than trusting the interface alone.
A terminal UI can make frequent operations quicker, but it should not hide the consequences of a rebase, force-push, or reset. Keep the command-line equivalent and a recovery path documented. The best choice is the one that helps your team understand Git while reducing routine friction.
Akousa