zaquestion
Please document installation as `git lab` rather than just `lab` or `git`
The README suggests installing the command as lab, and then optionally aliasing git to that. But as with git-hub, another option is to install the command as git-lab, and then use it as git lab; for instance, git lab mr create.
@joshtriplett, this will be addressed in large by the 1.0 release. We'll be updating lab to no longer operate as a wrapper and install this way by default. From there we may prompt the user on setup to automatically setup aliases within git to mimic the wrapped behavior.
Ill add some instructions on how to set lab up this way in the meantime. I may just post them here tho, as I'm inclined to think users who know they want this already know what to do.
I personally think that instructing lab users to add lab as alias is better than install lab as git-lab. When I see something using git-* as name I tend to imagine it uses the git infrastructure as a whole, which isn't true in our case. Lab operates heavily on GitLab API and uses same basic principles and features from git, like the concept of remotes and branches, but that's it. Overall, there isn't any interaction with git other than calling it directly as a cli tool for some really specific cases.
