Re: New tool for salsa
Le 02/11/2018 à 15:07, Xavier a écrit :
> Le 28/10/2018 à 23:06, Xavier a écrit :
>> Le 28/10/2018 à 19:38, Jochen Sprickerhof a écrit :
>>> Hi Xavier,
>>> thanks for doing this, it looks awesome :).
>> Thanks ;-)
>>> Would it make sense to split this into a Gitlab part and a Salsa only
>>> part? There are already a number of Gitlab tools (even in Debian) and
>>> commands like search_user sound rather generic, so maybe it would make
>>> sense to add them to those tools instead (I haven't checked if they
>>> provide similar commands already).
>> Salsa is based on common Devscripts::* library. Splitting it will be a
>> sort of fork. Anyway, any default values can be overridden in a file
>> (using --conf-file) so you can have a configuration file for each Gitlab
>>> * Xavier <email@example.com> [2018-10-28 11:44]:
>>>> A point must be decided: for now it is called simply "salsa". Like
>>>> "bts", it's a bit generic but nice, short and clear; but it can be used
>>>> to manage any GitLab instance.
>>> +1 for salsa.
>>> Speaking of it, I'm still looking for a hub like tool for Gitlab, most
>>> of the time I only need hub fork and hub pull-request. Is there a tool
>>> in Debian with this functions for Gitlab?
>> I'm going to insert this.
> Done in last commit. Example
> $ salsa fork node-mongodb
> $ cd node-mongodb
> $ git checkout -b fix-0000
> $ # Modify something
> $ git commit -a -m 'Fix something' -m 'Closes: #0000'
> $ salsa mr --mr-remove-source-branch
> New MR is created using your last commit!
$ salsa fork js-team/node-mongodb
$ cd node-mongodb
$ git checkout -b fix-0000
$ # Modify something
$ git commit -a -m 'Fix something' -m 'Closes: #0000'
$ salsa mr --mr-remove-source-branch
The name "salsa" seems to have been accepted unanimously (2/2) and
therefore seems accepted ;-)
> Many options available:
> Yo use salsa with another GitLab instance:
>>> (If you don't spit the salsa tool as proposed above, this would be a
>>> nice addition. That's why I ask here.)
> Done ;-)
>>> Cheers Jochen