> I think HighFlux is designed to solve a very limited subset of Git's usage and so they've stripped out a lot of useful commands they don't use and so they can ship a product.
Yes and no. No - once you correlate the user intent with the git commands, you discover that to accomplish one "intent," such as "start working on a feature," - you only need one CLI/UI command: "create WIP". So naturally, many git commands are bundled into one user intent.
Yes - true - we're just starting, so naturally focusing on the most used scenarios, gradually covering more and more cases as we progress. The nice thing is that HighFlux is not only compatible with git but also inter-operable with it, so you can always "go back to git" - until we cover all of the scenarios.