"gl track - start tracking changes to files" That tracking concept is worse than Git's staging area. It expects you to know what to track before making your ch

"gl track - start tracking changes to files" That tracking concept is worse than Git's staging area. It expects you to know what to track before making your changes which is almost never the case. Maybe you can track after the fact; then, it just becomes an alias for `git add`. Why confuse people with this? How is this simpler? "You can stop tracking changes to a tracked file with the gl untrack command" Does that mean if I stop tracking, the rest of my changes will be ignored, or that file will be excluded from the upcoming commit? What happens if I track a file for a brief period of time, but edit it before and after tracking? What would I be committing then? Am I expected to understand how this works in order to keep a decent commit history? "You can always revert a file back to some previous version with the gl checkout command." So, use a command that's entirely different ("checkout") than the intention ("reverting"). Sounds like Git to me. How is this better? Git CLI is bad, yes, this seems to be no improvement whatsoever.