You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Heroku seems to be encouraging people to use https://git.heroku.com/ repo URIs rather than [email protected]: URIs, i.e., https instead of ssh. Heroku_san should at least allow this as an option, if not make it the default.
Note that this would fix #165, a long-standing bug which really deserves a better fix than a workaround buried in the comments of an open issue. Since Heroku now supports and recommends the accounts plugin to the toolbelt, heroku_san should be able to deal with it.
The text was updated successfully, but these errors were encountered:
I agree! I've been unable to work on this fix for months, but maybe today
is the day. I have some time off :-)
On Mon, Dec 28, 2015 at 10:44 AM, Jonathan Kamens [email protected]
wrote:
Heroku seems to be encouraging people to use https://git.heroku.com/ repo
URIs rather than [email protected]: URIs, i.e., https instead of ssh.
Heroku_san should at least allow this as an option, if not make it the
default.
Note that this would fix #165 #165, a
long-standing bug which really deserves a better fix than a workaround
buried in the comments of an open issue. Since Heroku now supports and
recommends the accounts plugin to the toolbelt, heroku_san should be able
to deal with it.
—
Reply to this email directly or view it on GitHub #173.
Heroku seems to be encouraging people to use https://git.heroku.com/ repo URIs rather than [email protected]: URIs, i.e., https instead of ssh. Heroku_san should at least allow this as an option, if not make it the default.
Note that this would fix #165, a long-standing bug which really deserves a better fix than a workaround buried in the comments of an open issue. Since Heroku now supports and recommends the accounts plugin to the toolbelt, heroku_san should be able to deal with it.
The text was updated successfully, but these errors were encountered: