@bower/contributors Please review and test

Looking at it.

Even though I couldn't replicate the issue, the code still looks like the solution.
That said, not tested but still confident it will solve the issue. 🚢

Sorry, taking time to understand. Not really at ease with bower architecture yet.

By the way, we need to make sure bower is working for old git versions (e.g. there is no blocking in interactive mode when repository doesn't exist..)

For me it is pulling fromhttps://github (instead of git://) with this change.

small point:
this is the longest running test, it may time out on some machines:
✓ should recognize git remote endpoints correctly (2012ms at worst) (ranged from 990ms - 2300ms)
✓ should recognize GitHub endpoints correctly (1722ms at worst) (ranged from 900ms to 1700ms)
(I tested on multiple machines and noted the time taken ranges above, the worst time was taken from a 3 year old macbook air)

FWIW: This change nicely broke all our setups in Travis that had bower get stuff from private repositories. Previously we needed this configuration to make sure SSH authentication is used:

git config --global url.ssh://git@github.com/Collaborne/.insteadOf git://github.com/Collaborne/

With the change in resolvers we now have to fix all configurations to have redirects for both git:// and https://.