3 ms·

Why should I favor this over Github's hub? https://github.com/github/hub https://github.com/github/hub

• fiatjaf 11y ago
  This is much more complete, and also you know when you are doing GitHub things and when you are doing Git things.
• jessedhillon 11y ago
  > hub is best aliased as git, so you can type $ git <command> I'd rather have a git subcommand to interface with github. The way hub works is to alias over git and make it do github things by default. That seems like an obviously wrong way to do it.
  • jschwartzi 11y ago
    You could probably wrap it with another BASH script named git that looks for hub as $1, otherwise it passes its args directly into the git command. I haven't quite worked out how $PATH resolution would work in that scheme though.
    • jessedhillon 11y ago
      Git already works like this. If you attempt `git foo`, your $PATH will be consulted for an executable with the name `git-foo`, and if found, it will be called with the rest of the arguments. That's why this command is `git-hub` and is invoked with `git hub`.