On 2019-02-11 22:20:58, Xavier wrote:
> Le 11/02/2019 à 21:00, Antoine Beaupre a écrit :
>> Package: devscripts
>> Version: 2.19.2
>> Severity: normal
>> File: /usr/bin/salsa
>>
>> I can't use the `salsa fork` command for some reason:
>>
>> anarcat@curie:cron(master)$ git remote -v
>> origin https://salsa.debian.org/webmaster-team/cron/ (fetch)
>> origin https://salsa.debian.org/webmaster-team/cron/ (push)
>> anarcat@curie:cron(master)$ salsa fork
>> The #1 argument ($project_id) to fork_project must be a scalar at
>> /usr/share/perl5/Devscripts/Salsa/fork.pm line 14.
>>
>> I would have expected that command to:
>>
>> 1. hit that "Fork" button on the website, into my own namespace
>> (anarcat/cron?)
>>
>> 2. create a remote named "anarcat" pointing to those
>>
>> 3. update that remote
>>
>> A.
>
> Hello,
>
> you must specify what you want to fork in a non git repository:
>
> $ salsa fork webmaster-team/cron
>
> This creates fork on website and then launch
> "git clone git:@salsa.debian.org:<your-account>/cron && gbp pull"
>
> I'll update doc
That's better, but shouldn't salsa be able to figure that out on its own
based on the current project's remotes?
A.
--
The good news about computers is that they do what you tell them to
do. The bad news is that they do what you tell them to do.
- Ted Nelson
