1SALSA(1)                                                              SALSA(1)
2
3
4

NAME

6       salsa - tool to manipulate salsa repositories and group members
7

SYNOPSIS

9         # salsa <command> <args>
10         salsa whoami
11         salsa search_project devscripts
12         salsa search_project qa/qa
13         salsa search_group js-team
14         salsa search_group perl-team/modules
15         salsa search_user yadd
16         salsa push_repo . --group js-team --kgb --irc devscripts --tagpending
17         salsa update_repo node-mongodb --group js-team --disable-kgb --desc \
18               --desc-pattern "Package %p"
19         salsa update_repo js-team/node-mongodb --kgb --irc debian-js
20         salsa update_safe --all --desc --desc-pattern "Debian package %p" \
21               --group js-team
22         salsa checkout node-mongodb --group js-team
23         salsa checkout js-team/node-mongodb
24         salsa add_user developer foobar --group-id 2665
25         salsa update_user maintainer foobar --group js-team
26         salsa del_user foobar --group js-team
27         salsa last_ci_status js-team/nodejs
28         salsa pipelines js-team/nodejs
29

DESCRIPTION

31       salsa is designed to create and configure repositories on
32       <https://salsa.debian.org> and manage users of groups.
33
34       A Salsa token is required, except for search* commands, and must be set
35       in command line (see below), or in your configuration file
36       (~/.devscripts):
37
38         SALSA_TOKEN=abcdefghi
39
40       or
41
42         SALSA_TOKEN=`cat ~/.token`
43
44       or
45
46         SALSA_TOKEN_FILE=~/.dpt.conf
47
48       If you choose to link another file using SALSA_TOKEN_FILE, it must
49       contain a line with one of (no differences):
50
51         <anything>SALSA_PRIVATE_TOKEN=xxxx
52         <anything>SALSA_TOKEN=xxxx
53
54       This allows for example to use dpt(1) configuration file (~/.dpt.conf)
55       which contains:
56
57         DPT_SALSA_PRIVATE_TOKEN=abcdefghi
58

COMMANDS

60   Managing users and groups
61       join
62           Request access to a group.
63
64             salsa join js-team
65             salsa join --group js-team
66             salsa join --group-id 1234
67
68       add_user
69           Add a user to a group.
70
71             salsa --group js-group add_user guest foouser
72             salsa --group-id 1234 add_user guest foouser
73             salsa --group-id 1234 add_user maintainer 1245
74
75           First argument is the GitLab's access levels: guest, reporter,
76           developer, maintainer, owner.
77
78       del_user
79           Remove a user from a group
80
81             salsa --group js-team del_user foouser
82             salsa --group-id=1234 del_user foouser
83
84       list_groups
85           List sub groups of current one if group is set, groups of current
86           user else.
87
88       group
89           Show group members.
90
91             salsa --group js-team group
92             salsa --group-id 1234 group
93
94       search_group
95           Search for a group using given string. Shows group id and other
96           information.
97
98             salsa search_group perl-team
99             salsa search_group perl-team/modules
100             salsa search_group 2666
101
102       search_user
103           Search for a user using given string. Shows user id and other
104           information.
105
106             salsa search_user yadd
107
108       update_user
109           Update user role in a group.
110
111             salsa --group-id 1234 update_user guest foouser
112             salsa --group js-team update_user maintainer 1245
113
114           First argument is the GitLab's access levels: guest, reporter,
115           developer, maintainer, owner.
116
117       whoami
118           Gives information on the token owner
119
120             salsa whoami
121
122   Managing repositories
123       One of "--group", "--group-id", "--user" or "--user-id" is required to
124       manage repositories. If both are set, salsa warns and only
125       "--user"/"--user-id" is used. If none is given, salsa uses current user
126       id (token owner).
127
128       check_repo
129           Verify that repo(s) are well configured. It works exactly like
130           update_repo except that it does not modify anything but just lists
131           projects not well configured with found errors.
132
133             salsa --user yadd --tagpending --kgb --irc=devscripts check_repo test
134             salsa --group js-team check_repo --all
135             salsa --group js-team --rename-head check_repo test1 test2 test3
136
137       checkout or co
138           Clone repo in current dir. If directory already exists, update
139           local repo.
140
141             salsa --user yadd co devscripts
142             salsa --group js-team co node-mongodb
143             salsa co js-team/node-mongodb
144
145           You can clone more than one repository or all repositories of a
146           group or a user:
147
148             salsa --user yadd co devscripts autodep8
149             salsa co yadd/devscripts js-team/npm
150             salsa --group js-team co --all           # All js-team active repos
151             salsa co --all-archived                  # All your repos including archived
152
153       create_repo
154           Create public empty project. If "--group"/"--group-id" is set,
155           project is created in group directory, else in user directory.
156
157             salsa --user yadd create_repo test
158             salsa --group js-team --kgb --irc-channel=devscripts create_repo test
159
160       del_repo
161           Delete a repository.
162
163       fork
164           Forks a project in group/user repository and set "upstream" to
165           original project. Example:
166
167             $ salsa fork js-team/node-mongodb --verbose
168             ...
169             salsa.pl info: node-mongodb ready in node-mongodb/
170             $ cd node-mongodb
171             $ git remote --verbose show
172             origin          git@salsa.debian.org:me/node-mongodb (fetch)
173             origin          git@salsa.debian.org:me/node-mongodb (push)
174             upstream        git@salsa.debian.org:js-team/node-mongodb (fetch)
175             upstream        git@salsa.debian.org:js-team/node-mongodb (push)
176
177           For a group:
178
179             salsa fork --group js-team user/node-foo
180
181       forks
182           List forks of project(s).
183
184             salsa forks qa/qa debian/devscripts
185
186           Project can be set using full path or using --group/--group-id or
187           --user/--user-id, else it is searched in current user namespace.
188
189       push
190           Push relevant packaging refs to origin Git remote. To be run from
191           packaging working directory.
192
193             salsa push
194
195           It pushes the following refs to the configured remote for the
196           debian-branch or, falling back, to the "origin" remote:
197
198           "master" branch (or whatever is set to debian-branch in gbp.conf)
199           "upstream" branch (or whatever is set to upstream-branch in
200           gbp.conf)
201           "pristine-tar" branch
202           tags named "debian/*" (or whatever is set to debian-tag in
203           gbp.conf)
204           tags named "upstream/*" (or whatever is set to upstream-tag in
205           gbp.conf)
206           all tags, if the package's source format is "3.0 (native)"
207       ls or list_repos
208           Shows projects owned by user or group. If second argument exists,
209           search only matching projects
210
211             salsa --group js-team list_repos
212             salsa --user yadd list_repos foo*
213
214       last_ci_status or ci
215           Displays last continuous integration result. Use --verbose to see
216           URL of pipeline when result isn't success. Unless --no-fail is set,
217           salsa last_ci_status will stop on first "failed" status.
218
219             salsa --group js-team last_ci_status --all --no-fail
220             salsa --user yadd last_ci_status foo
221             salsa last_ci_status js-team/nodejs
222
223           This commands returns the number of "failed" status found.
224           "success" entries are displayed using STDOUT while other are
225           displayed (with details) using STDERR. Then you can easily see only
226           failures using:
227
228             salsa --group js-team last_ci_status --all --no-fail >/dev/null
229
230       pipeline, schedule
231           Control pipeline schedule
232
233       pipelines, schedules
234           Lists current pipeline schedule items.
235
236           You can use --no-fail and --all options here.
237
238       merge_request, mr
239           Creates a merge request.
240
241           Suppose you created a fork using salsa fork, modify some things in
242           a new branch using one commit and want to propose it to original
243           project (branch "master"). You just have to launch this in source
244           directory:
245
246             salsa mr
247
248           Other example:
249
250             salsa mr --mr-dst-project debian/foo --mr-dst-branch debian/master
251
252           or simply
253
254             salsa mr debian/foo debian/master
255
256           Note that unless destination project has been set using command
257           line, salsa merge_request will search it in the following order:
258
259           using GitLab API: salsa will detect from where this project was
260           forked
261           using "upstream" origin
262           else salsa will use source project as destination project
263
264           To force salsa to use source project as destination project, you
265           can use "same":
266
267             salsa mr --mr-dst-project same
268             # or
269             salsa mr same
270
271           New merge request will be created using last commit title and
272           description.
273
274           See --mr-* options for more.
275
276       merge_requests, mrs
277           List opened merge requests for project(s)
278
279             salsa mrs qa/qa debian/devscripts
280
281           Project can be set using full path or using --group/--group-id or
282           --user/--user-id, else it is searched in current user namespace.
283
284       protect_branch
285           Protect/unprotect a branch.
286
287           Set protection
288                 #                                    project      branch merge push
289                 salsa --group js-team protect_branch node-mongodb master m     d
290
291               "merge" and "push" can be one of:
292
293               o, owner: owner only
294               m, maintainer: o + maintainers allowed
295               d, developer: m + developers allowed
296               r, reporter: d + reporters allowed
297               g, guest: r + guest allowed
298           Unprotect
299                 salsa --group js-team protect_branch node-mongodb master no
300
301       protected_branches
302           List protected branches
303
304             salsa --group js-team protected_branches node-mongodb
305
306       push_repo
307           Create a new project from a local Debian source directory
308           configured with git.
309
310           push_repo executes the following steps:
311
312           gets project name using debian/changelog file;
313           launches git remote add upstream ...;
314           launches create_repo;
315           pushes local repo.
316
317           Examples:
318
319             salsa --user yadd push_repo ./test
320             salsa --group js-team --kgb --irc-channel=devscripts push_repo .
321
322       rename_branch
323           Rename branch given in --source-branch with name given in
324           --dest-branch.  You can use --no-fail, --all and --all-archived
325           options here.
326
327       search, search_project, search_repo
328           Search for a project using given string. Shows name, owner id and
329           other information.
330
331             salsa search devscripts
332             salsa search debian/devscripts
333             salsa search 18475
334
335       update_repo
336           Configure repo(s) using parameters given to command line.  A repo
337           name has to be given unless --all or --all-archived is set. Prefer
338           to use update_safe.
339
340             salsa --user yadd --tagpending --kgb --irc=devscripts update_repo test
341             salsa --group js-team update_repo --all
342             salsa --group js-team --rename-head update_repo test1 test2 test3
343             salsa update_repo js-team/node-mongodb --kgb --irc debian-js
344
345           By default when using --all, salsa will fail on first error. If you
346           want to continue, set --no-fail. In this case, salsa will display a
347           warning for each project that has fail but continue with next
348           project. Then to see full errors, set --verbose.
349
350       update_safe
351           Launch check_repo and ask before launching update_repo (unless
352           --yes).
353
354             salsa --user yadd --tagpending --kgb --irc=devscripts update_safe test
355             salsa --group js-team update_safe --all
356             salsa --group js-team --rename-head update_safe test1 test2 test3
357             salsa update_safe js-team/node-mongodb --kgb --irc debian-js
358
359   Other
360       purge_cache
361           Empty local cache.
362

OPTIONS

364   General options
365       -C, --chdir
366           Change directory before launching command
367
368             salsa -C ~/debian co debian/libapache2-mod-fcgid
369
370       --cache-file
371           File to store cached values. Default to ~/.cache/salsa.json. An
372           empty value disables cache.
373
374           ".devscripts" value: SALSA_CACHE_FILE
375
376       --no-cache
377           Disable cache usage. Same as --cache-file ''
378
379       --conffile, --conf-file
380           Add or replace default configuration files ("/etc/devscripts.conf"
381           and "~/.devscripts"). This can only be used as the first option
382           given on the command-line.
383
384           replace:
385                 salsa --conf-file test.conf <command>...
386                 salsa --conf-file test.conf --conf-file test2.conf  <command>...
387
388           add:
389                 salsa --conf-file +test.conf <command>...
390                 salsa --conf-file +test.conf --conf-file +test2.conf  <command>...
391
392               If one --conf-file has no "+", default configuration files are
393               ignored.
394
395       --no-conf, --noconf
396           Don't read any configuration files. This can only be used as the
397           first option given on the command-line.
398
399       --debug
400           Enable debugging output
401
402       --group
403           Team to use. Use "salsa search_group name" to find it.
404
405           If you want to use a subgroup, you have to set its full path:
406
407             salsa --group perl-team/modules/packages check_repo lemonldap-ng
408
409           ".devscripts" value: SALSA_GROUP
410
411           Be careful when you use SALSA_GROUP in your ".devscripts" file.
412           Every salsa command will be executed in group space, for example if
413           you want to propose a little change in a project using salsa fork +
414           salsa mr, this "fork" will be done in group space unless you set a
415           --user/--user-id.  Prefer to use an alias in your ".bashrc" file.
416           Example:
417
418             alias jsteam_admin="salsa --group js-team"
419
420           or
421
422             alias jsteam_admin="salsa --conf-file ~/.js.conf
423
424           or to use both .devscripts and .js.conf:
425
426             alias jsteam_admin="salsa --conf-file +~/.js.conf
427
428           then you can fix SALSA_GROUP in "~/.js.conf"
429
430           To enable bash completion for your alias, add this in your .bashrc
431           file:
432
433             _completion_loader salsa
434             complete -F _salsa_completion jsteam_admin
435
436       --group-id
437           Group id to use. Use "salsa search_group name" to find it.
438
439           ".devscripts" value: SALSA_GROUP_ID
440
441           Be careful when you use SALSA_GROUP_ID in your ".devscripts" file.
442           Every salsa command will be executed in group space, for example if
443           you want to propose a little change in a project using salsa fork +
444           salsa mr, this "fork" will be done in group space unless you set a
445           --user/--user-id.  Prefer to use an alias in your ".bashrc" file.
446           Example:
447
448             alias jsteam_admin="salsa --group-id 2666"
449
450           or
451
452             alias jsteam_admin="salsa --conf-file ~/.js.conf
453
454           then you can fix SALSA_GROUP_ID in "~/.js.conf"
455
456       --help: displays this manpage
457       -i, --info
458           Prompt before sensible changes.
459
460           ".devscripts" value: SALSA_INFO (yes/no)
461
462       --path
463           Repo path. Default to group or user path.
464
465           ".devscripts" value: SALSA_REPO_PATH
466
467       --token
468           Token value (see above).
469
470       --token-file
471           File to find token (see above).
472
473       --user
474           Username to use. If neither --group, --group-id, --user or
475           --user-id is set, salsa uses current user id (corresponding to
476           salsa private token).
477
478       --user-id
479           User id to use. Use "salsa search_user name" to find one. If
480           neither --group, --group-id, --user or --user-id is set, salsa uses
481           current user id (corresponding to salsa private token).
482
483           ".devscripts" value: SALSA_USER_ID
484
485       --verbose
486           Enable verbose output.
487
488       --yes
489           Never ask for consent.
490
491           ".devscripts" value: SALSA_YES (yes/no)
492
493   List/search repo options
494       --archived, --no-archived
495           Instead of looking to active projects, list or search in archived
496           projects.  Note that you can't have both archived and unarchived
497           projects in the same request. Default: no (ie --no-archived).
498
499           ".devscripts" value: SALSA_ARCHIVED (yes/no)
500
501   Update/create repo options
502       --all, --all-archived
503           When set, all projects of group/user are affected by command.
504           --all will filter all active projects, whereas --all-archived will
505           include active and archived projects.
506
507           --skip: ignore project with --all or --all-achived. Example:
508                 salsa update_repo --tagpending --all --skip qa --skip devscripts
509
510               ".devscripts" value: SALSA_SKIP. To set multiples values, use
511               spaces.  Example
512
513                 SALSA_SKIP=qa devscripts
514
515           --skip-file: ignore projects in this file (1 project per line)
516                 salsa update_repo --tagpending --all --skip-file ~/.skip
517
518               ".devscripts" value: SALSA_SKIP_FILE
519
520       --build-timeout
521           The maximum amount of time, in seconds, that a job can run.
522
523           Default: 3600 (60 minutes)
524
525             salsa update_safe myrepo --build-timeout 3600
526
527           ".devscripts" value: SALSA_BUILD_TIMEOUT
528
529       --avatar-path
530           Path to an image for the project's avatar.  If path value contains
531           "%p", it is replaced by project name.
532
533           ".devscripts" value: SALSA_AVATAR_PATH
534
535       --ci-config-path
536           Configure configuration file path of GitLab CI. Default: empty.
537           Example:
538
539             salsa update_safe --ci-config-path recipes/debian.yml@salsa-ci-team/pipeline debian/devscripts
540
541           ".devscripts" value: SALSA_CI_CONFIG_PATH
542
543       --desc, --no-desc
544           Configure repo description using pattern given in desc-pattern
545
546           ".devscripts" value: SALSA_DESC (yes/no)
547
548       --desc-pattern
549           Repo description pattern. Default to "Debian package %p". "%p" is
550           replaced by repo name, while "%P" is replaced by repo name given in
551           command (may contains full path).
552
553           ".devscripts" value: SALSA_DESC_PATTERN
554
555       --email, --no-email, --disable-email
556           Enable, ignore or disable email-on-push.
557
558           ".devscripts" value: SALSA_EMAIL (yes/ignore/no, default: ignore)
559
560       --email-recipient
561           Email-on-push recipient. Can be multi valued:
562
563             $ salsa update_safe myrepo \
564                   --email-recipient foo@foobar.org \
565                   --email-recipient bar@foobar.org
566
567           If recipient value contains "%p", it is replaced by project name.
568
569           ".devscripts" value: SALSA_EMAIL_RECIPIENTS (use spaces to separate
570           multiples recipients)
571
572       --issues
573           Set issues feature with permissions.
574
575           ".devscripts" values: SALSA_ENABLE_ISSUES (yes/private/no, default:
576           yes)
577
578       --repo
579           Set repository feature with permissions.
580
581           ".devscripts" values: SALSA_ENABLE_REPO (yes/private/no, default:
582           yes)
583
584       --mr
585           Set merge requests feature with permissions.
586
587           ".devscripts" values: SALSA_ENABLE_MR (yes/private/no, default:
588           yes)
589
590       --forks, --forks-mr
591           Set forking a repository feature with permissions.
592
593           ".devscripts" values: SALSA_ENABLE_FORKS (yes/private/no, default:
594           yes)
595
596       --lfs
597           Set Large File Storage (LFS) feature.
598
599           ".devscripts" values: SALSA_ENABLE_LFS (yes/no, default: yes)
600
601       --packages
602           Set packages feature.
603
604           ".devscripts" values: SALSA_ENABLE_PACKAGING (yes/no, default: yes)
605
606       --jobs
607           Set jobs feature with permissions.
608
609           ".devscripts" values: SALSA_ENABLE_JOBS (yes/private/no, default:
610           yes)
611
612       --container
613           Set container feature with permissions.
614
615           ".devscripts" values: SALSA_ENABLE_CONTAINER (yes/private/no,
616           default: yes)
617
618       --analytics
619           Set analytics feature with permissions.
620
621           ".devscripts" values: SALSA_ENABLE_ANALYTICS (yes/private/no,
622           default: yes)
623
624       --requirements
625           Set requirements feature with permissions.
626
627           ".devscripts" values: SALSA_ENABLE_REQUIREMENTS (yes/private/no,
628           default: yes)
629
630       --wiki
631           Set wiki feature with permissions.
632
633           ".devscripts" values: SALSA_ENABLE_WIKI (yes/private/no, default:
634           yes)
635
636       --snippets
637           Set snippets feature with permissions.
638
639           ".devscripts" values: SALSA_ENABLE_SNIPPETS (yes/private/no,
640           default: yes)
641
642       --pages
643           Set pages feature with permissions.
644
645           ".devscripts" values: SALSA_ENABLE_PAGES (yes/private/no, default:
646           yes)
647
648       --releases
649           Set releases feature with permissions.
650
651           ".devscripts" values: SALSA_ENABLE_RELEASES (yes/private/no,
652           default: yes)
653
654       --auto-devops
655           Set auto devops feature.
656
657           ".devscripts" values: SALSA_ENABLE_AUTO_DEVOPS (yes/no, default:
658           yes)
659
660       --request-acc
661           Set request access feature.
662
663           ".devscripts" values: SALSA_ENABLE_REQUEST_ACC (yes/no, default:
664           yes)
665
666       --enable-remove-source-branch, --disable-remove-source-branch
667           Enable or disable deleting source branch option by default for all
668           new merge requests.
669
670           ".devscripts" values: SALSA_REMOVE_SOURCE_BRANCH (yes/no, default:
671           yes)
672
673       --irc-channel
674           IRC channel for KGB or Irker. Can be used more than one time only
675           with --irker.
676
677           Important: channel must not include the first "#". If salsa finds a
678           channel starting with "#", it will consider that the channel starts
679           with 2 "#"!
680
681           ".devscript" value: SALSA_IRC_CHANNEL.
682
683           Multiple values must be space separated.
684
685           Since configuration files are read using sh, be careful when using
686           "#": you must enclose the channel with quotes, else sh will
687           consider it as a comment and will ignore this value.
688
689       --irker, --no-irker, --disable-irker
690           Enable, ignore or disable Irker service
691
692           ".devscripts" values: SALSA_IRKER (yes/ignore/no, default: ignore)
693
694       --irker-host
695           Irker host. Default: ruprecht.snow-crash.org
696
697           ".devscripts" value: SALSA_IRKER_HOST
698
699       --irker-port
700           Irker port. Default: empty (default value)
701
702           ".devscripts" value: SALSA_IRKER_PORT
703
704       --kgb, --no-kgb, --disable-kgb
705           Enable, ignore or disable KGB webhook.
706
707           ".devscripts" value: SALSA_KGB (yes/ignore/no, default: ignore)
708
709       --kgb-options
710           List of KGB enabled options (comma separated). Default:
711           issues_events, merge_requests_events, note_events, pipeline_events,
712           push_events, tag_push_events, wiki_page_events,
713           enable_ssl_verification
714
715             $ salsa update_safe debian/devscripts --kgb --irc-channel devscripts \
716               --kgb-options 'merge_requests_events,issues_events,enable_ssl_verification'
717
718           List of available options: confidential_comments_events,
719           confidential_issues_events, confidential_note_events,
720           enable_ssl_verification, issues_events, job_events,
721           merge_requests_events, note_events, pipeline_events,
722           tag_push_events, wiki_page_events
723
724           ".devscripts" value: SALSA_KGB_OPTIONS
725
726       --no-fail
727           Don't stop on error when using update_repo with --all or
728           --all-archived.
729
730           ".devscripts" value: SALSA_NO_FAIL (yes/no)
731
732       --request-access
733           Allow users to request member access.
734
735           ".devscripts" value: SALSA_REQUEST_ACCESS (yes/no)
736
737       --rename-head, --no-rename-head
738           Rename HEAD branch given by --source-branch into --dest-branch and
739           change "default branch" of project. Works only with update_repo.
740
741           ".devscripts" value: SALSA_RENAME_HEAD (yes/no)
742
743           --source-branch: default "master"
744               ".devscripts" value: SALSA_SOURCE_BRANCH
745
746           --dest-branch: default "debian/master"
747               ".devscripts" value: SALSA_DEST_BRANCH
748
749       --tagpending, --no-tagpending, --disable-tagpending
750           Enable, ignore or disable "tagpending" webhook.
751
752           ".devscripts" value: SALSA_TAGPENDING (yes/ignore/no, default:
753           ignore)
754
755   Pipeline schedules
756       --schedule-desc
757           Description of the pipeline schedule.
758
759       --schedule-ref
760           Branch or tag name that is triggered.
761
762       --schedule-cron
763           Cron schedule, for example: 0 1 * * *.
764
765       --schedule-tz
766           Time zone to run cron schedule. Default: UTC
767
768       --schedule-enable, --schedule-disable
769           Enable/disable the pipeline schedule to run. Default: disabled
770
771       --schedule-run
772           Trigger --schedule-desc scheduled pipeline to run immediately.
773           Default:
774
775       --schedule-delete
776           Delete --schedule-desc pipeline schedule
777
778   Merge requests options
779       --mr-title
780           Title for merge request. Default: last commit title.
781
782       --mr-desc
783           Description of new MR. Default:
784
785           empty if --mr-title is set
786           last commit description if any
787       --mr-dst-branch (or second command line argument)
788           Destination branch. Default to "master".
789
790       --mr-dst-project (or first command line argument)
791           Destination project. Default: project from which the current
792           project was forked; or, if not found, "upstream" value found using
793           git remote --verbose show; or using source project.
794
795           If --mr-dst-project is set to same, salsa will use source project
796           as destination.
797
798       --mr-src-branch
799           Source branch. Default: current branch.
800
801       --mr-src-project
802           Source project. Default: current project found using git remote
803           --verbose show.
804
805       --mr-allow-squash, --no-mr-allow-squash
806           Allow upstream project to squash your commits, this is the default.
807
808           ".devscripts" value: SALSA_MR_ALLOW_SQUASH (yes/no)
809
810       --mr-remove-source-branch, --no-mr-remove-source-branch
811           Remove source branch if merge request is accepted. Default: no.
812
813           ".devscripts" value: SALSA_MR_REMOVE_SOURCE_BRANCH (yes/no)
814
815   Options to manage other Gitlab instances
816       --api-url
817           GitLab API. Default: <https://salsa.debian.org/api/v4>.
818
819           ".devscripts" value: SALSA_API_URL
820
821       --git-server-url
822           Default to "git@salsa.debian.org:"
823
824           ".devscripts" value: SALSA_GIT_SERVER_URL
825
826       --irker-server-url
827           Default to "ircs://irc.oftc.net:6697/"
828
829           ".devscripts" value: SALSA_IRKER_SERVER_URL
830
831       --kgb-server-url
832           Default to <http://kgb.debian.net:9418/webhook/?channel=>
833
834           ".devscripts" value: SALSA_KGB_SERVER_URL
835
836       --tagpending-server-url
837           Default to <https://webhook.salsa.debian.org/tagpending/>
838
839           ".devscripts" value: SALSA_TAGPENDING_SERVER_URL
840
841       Configuration file example
842
843       Example to use salsa with <https://gitlab.ow2.org> (group "lemonldap-
844       ng"):
845
846         SALSA_TOKEN=`cat ~/.ow2-gitlab-token`
847         SALSA_API_URL=https://gitlab.ow2.org/api/v4
848         SALSA_GIT_SERVER_URL=git@gitlab.ow2.org:
849         SALSA_GROUP_ID=34
850
851       Then to use it, add something like this in your ".bashrc" file:
852
853         alias llng_admin='salsa --conffile ~/.salsa-ow2.conf'
854

SEE ALSO

856       dpt-salsa
857

AUTHOR

859       Xavier Guimard <yadd@debian.org>
860
862       Copyright (C) 2018, Xavier Guimard <yadd@debian.org>
863
864       It contains code formerly found in dpt-salsa (pkg-perl-tools) copyright
865       2018, gregor herrmann <gregoa@debian.org>.
866
867       This library is free software; you can redistribute it and/or modify it
868       under the terms of the GNU General Public License as published by the
869       Free Software Foundation; either version 2, or (at your option) any
870       later version.
871
872       This program is distributed in the hope that it will be useful, but
873       WITHOUT ANY WARRANTY; without even the implied warranty of
874       MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
875       General Public License for more details.
876
877       You should have received a copy of the GNU General Public License along
878       with this program.  If not, see <http://www.gnu.org/licenses/>.
879
880
881
882Debian Utilities                  2023-02-05                          SALSA(1)
Impressum