[Pharo-users] Pharo + git workflow

Norbert Hartl norbert at hartl.name
Tue Jan 26 07:32:15 EST 2016


> Am 26.01.2016 um 13:03 schrieb Norbert Hartl <norbert at hartl.name>:
> 
>> 
>> Am 25.01.2016 um 23:32 schrieb Thierry Goubier <thierry.goubier at gmail.com <mailto:thierry.goubier at gmail.com>>:
>> 
>> Le 25/01/2016 23:13, Norbert Hartl a écrit :
>>> 
>>>> Am 25.01.2016 um 23:02 schrieb Norbert Hartl <norbert at hartl.name <mailto:norbert at hartl.name>>:
>>>> 
>>>> Hi,
>>>> 
>>>>> Am 25.01.2016 um 22:55 schrieb Thierry Goubier <thierry.goubier at gmail.com <mailto:thierry.goubier at gmail.com>>:
>>>>> 
>>>>> Hi Norbert,
>>>>> 
>>>>> Just tell me if you need any additional parameter to the git clone for the credentials, because I'm not sure I have written the code which will handle them.
>>>>> 
>>>> I'll check that. The easiest approach is to use the authority part of the url like
>>>> 
>>>> https://user:pass@bitbucket.org/ <https://user:pass@bitbucket.org/>….
>> 
>> I'm nearly sure my code doesn't check for them and silently drop them :(
>> 
>>>> I try that tomorrow.
>>>> 
>>> But then I don't think that sub-directories work per http.
>> 
>> They do over https. But remember the syntax is, to take your url,
>> 
>> gitfiletree://user:pass@bitbucket.org/...?protocol=https <gitfiletree://user:pass@bitbucket.org/...?protocol=https>
> 
> Does not work for me. It complains about unknown url scheme. But using the read-only version of gitfiletree would still mean I have to install gitfiletree, no? I have no glue hot the url with bitbucket:// could work.
>> 
>> I wonder if I can write code that considers that if you have a username and a password, then it should use https and not ssh.
> 
> I see no reason why. You can use ssh with username and password as well.
> 
Ok, I got it through the unknown url scheme but indeed the credentials are stripped off.

Norbert

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/attachments/20160126/bef980f9/attachment.html>


More information about the Pharo-users mailing list