--- name: "salsa" section: "1" platform: "linux" package: "devscripts" version: "2.25.15+deb13u1" release: "Debian 13 (Trixie)" platforms: ["linux"] url: "https://new.carta.tech/salsa" --- # salsa(1) tool to manipulate salsa projects, repositories and group members ## NAME salsa - tool to manipulate salsa projects, repositories and group members ## SYNOPSIS ``` # salsa salsa add_user developer foobar --group-id 2665 salsa delete_user foobar --group js-team salsa search_groups perl-team/modules salsa search_projects qa/qa salsa search_users yadd salsa update_user maintainer foobar --group js-team salsa whoami salsa checkout node-mongodb --group js-team salsa fork salsa fork --group js-team user/node-foo salsa last_ci_status js-team/nodejs salsa pipelines js-team/nodejs salsa mr debian/foo debian/latest salsa push_repo . --group js-team --kgb --irc devscripts --tagpending salsa update_projects node-mongodb --group js-team --disable-kgb --desc \ --desc-pattern "Package %p" salsa update_safe --all --desc --desc-pattern "Debian package %p" \ --group js-team ``` ## DESCRIPTION **salsa** is designed to create and configure projects and repositories on \ as well as to manage group members. A Salsa token is required, except for search\* commands, and must be set in command line *(see below)*, or in your configuration file *(~/.devscripts)*: ``` SALSA_TOKEN=abcdefghi ``` or ``` SALSA_TOKEN=`cat ~/.token` ``` or ``` SALSA_TOKEN_FILE=~/.dpt.conf ``` If you choose to link another file using SALSA\_TOKEN\_FILE, it must contain a line with one of (no differences): ``` SALSA_PRIVATE_TOKEN=xxxx SALSA_TOKEN=xxxx ``` This allows for example to use [**dpt**(1)](/dpt/1.md) configuration file (~/.dpt.conf) which contains: ``` DPT_SALSA_PRIVATE_TOKEN=abcdefghi ``` ## COMMANDS ### Managing users and groups - **add\_user** Add a user to a group. ``` salsa --group js-group add_user guest foouser salsa --group-id 1234 add_user guest foouser salsa --group-id 1234 add_user maintainer 1245 ``` First argument is the GitLab's access levels: guest, reporter, developer, maintainer, owner. - **delete\_user** or **del\_user** Remove a user from a group. ``` salsa --group js-team delete_user foouser salsa --group-id=1234 delete_user foouser ``` - **join** Request access to a group. ``` salsa join js-team salsa join --group js-team salsa join --group-id 1234 ``` - **list\_groups** List the subgroups for current group if group is set, otherwise will do the current user. - **list\_users** or **group** List users in a subgroup. Note, this does not include inherited or invited. ``` salsa --group js-team list_users salsa --group-id 1234 list_users ``` - **search\_groups** Search for a group using given string. Shows group ID and other information. ``` salsa search_groups perl-team salsa search_groups perl-team/modules salsa search_groups 2666 ``` - **search\_users** Search for a user using given string. Shows user ID and other information. ``` salsa search_users yadd ``` - **update\_user** Update a user's role in a group. ``` salsa --group-id 1234 update_user guest foouser salsa --group js-team update_user maintainer 1245 ``` First argument is the GitLab's access levels: guest, reporter, developer, maintainer, owner. - **whoami** Gives information on the token owner. ``` salsa whoami ``` ### Managing projects One of `"--group"`, `"--group-id"`, `"--user"` or `"--user-id"` is required to manage projects. If both are set, salsa warns and only `"--user"`/`"--user-id"` is used. If none is given, salsa uses current user ID *(token owner)*. - **check\_projects** or **check\_repo** Verify that projects are configured as expected. It works exactly like **update\_projects** except that it does not modify anything but just lists projects not well configured with found errors. ``` salsa --user yadd --tagpending --kgb --irc=devscripts check_projects test salsa --group js-team check_projects --all salsa --group js-team --rename-head check_projects test1 test2 test3 ``` - **checkout** or **co** Clone a project's repository in current directory. If the directory already exists, update local repository. ``` salsa --user yadd checkout devscripts salsa --group js-team checkout node-mongodb salsa checkout js-team/node-mongodb salsa checkout https://salsa.debian.org/debian/devscripts.git ``` You can clone more than one repository or all repositories of a group or a user: ``` salsa --user yadd checkout devscripts autodep8 salsa checkout yadd/devscripts js-team/npm salsa --group js-team checkout --all # All js-team active repositories salsa checkout --all-archived # All your repositories, including archived ``` - **create\_project** or **create\_repo** Create public empty project. If `"--group"`/`"--group-id"` is set, project is created in group directory, else in user directory. ``` salsa --user yadd create_project test salsa --group js-team --kgb --irc-channel=devscripts create_project test ``` - **delete\_project** or **del\_repo** Delete a project. - **fork** Forks a project in group/user repository and set "upstream" to original project. Example: ``` $ salsa fork js-team/node-mongodb --verbose ... salsa.pl info: node-mongodb ready in node-mongodb/ $ cd node-mongodb $ git remote --verbose show origin git@salsa.debian.org:me/node-mongodb (fetch) origin git@salsa.debian.org:me/node-mongodb (push) upstream git@salsa.debian.org:js-team/node-mongodb (fetch) upstream git@salsa.debian.org:js-team/node-mongodb (push) ``` For a group: ``` salsa fork --group js-team user/node-foo ``` - **forks** List forks of project(s). ``` salsa forks qa/qa debian/devscripts ``` Project can be set using full path or using **--group**/**--group-id** or **--user**/**--user-id**, else it is searched in current user namespace. - **push** Push relevant packaging refs to origin Git remote. To be run from packaging working directory. ``` salsa push ``` It pushes the following refs to the configured remote for the debian-branch or, falling back, to the "origin" remote: - "master" branch (or whatever is set to debian-branch in gbp.conf) - "upstream" branch (or whatever is set to upstream-branch in gbp.conf) - "pristine-tar" branch - tags named "debian/\*" (or whatever is set to debian-tag in gbp.conf) - tags named "upstream/\*" (or whatever is set to upstream-tag in gbp.conf) - all tags, if the package's source format is "3.0 (native)" - **list\_projects** or **list\_repos** or **ls** Shows projects owned by user or group. If second argument exists, search only matching projects. ``` salsa --group js-team list_projects salsa --user yadd list_projects foo* ``` - **last\_ci\_status** Displays the last continuous integration result. Use **--verbose** to see URL of pipeline when result isn't **success**. Unless **--no-fail** is set, **salsa last\_ci\_status** will stop on first "failed" status. ``` salsa --group js-team last_ci_status --all --no-fail salsa --user yadd last_ci_status foo salsa last_ci_status js-team/nodejs ``` This commands returns the number of "failed" status found. "success" entries are displayed using STDOUT while other are displayed *(with details)* using STDERR. Then you can easily see only failures using: ``` salsa --group js-team last_ci_status --all --no-fail >/dev/null ``` - **pipeline\_schedule** or **schedule** Control pipeline schedule. - **pipeline\_schedules** or **schedules** Lists current pipeline schedule items. You can use **--no-fail** and **--all** options here. - **merge\_request** or **mr** Creates a merge request. Suppose you created a fork using **salsa fork**, modify some things in a new branch using one commit and want to propose it to original project *(branch "master")*. You just have to launch this in source directory: ``` salsa merge_request ``` Another example: ``` salsa merge_request --mr-dst-project debian/foo --mr-dst-branch debian/latest ``` Or simply: ``` salsa merge_request debian/foo debian/latest ``` Note that unless destination project has been set using command line, **salsa merge\_request** will search it in the following order: - using GitLab API: salsa will detect from where this project was forked - using "upstream" origin - else salsa will use source project as destination project To force salsa to use source project as destination project, you can use "same": ``` salsa merge_request --mr-dst-project same # or salsa merge_request same ``` New merge request will be created using last commit title and description. See **--mr-\*** options for more. - **merge\_requests** or **mrs** List opened merge requests for project(s). ``` salsa merge_requests qa/qa debian/devscripts ``` Project can be set using full path or using **--group**/**--group-id** or **--user**/**--user-id**, else it is searched in current user namespace. - **protect\_branch** Protect/unprotect a branch. - Protect ``` # project branch merge push salsa --group js-team protect_branch node-mongodb master m d ``` "merge" and "push" can be one of: - **o**, **owner**: owner only - **m**, **maintainer**: **o** + maintainers allowed - **d**, **developer**: **m** + developers allowed - **r**, **reporter**: **d** + reporters allowed - **g**, **guest**: **r** + guest allowed - Unprotect ``` salsa --group js-team protect_branch node-mongodb master no ``` - **protected\_branches** List protected branches: ``` salsa --group js-team protected_branches node-mongodb ``` - **push\_repo** Create a new project from a local Debian source directory configured with git. **push\_repo** executes the following steps: - gets project name using debian/changelog file; - launches **git remote add upstream ...**; - launches **create\_project**; - pushes local repository. Examples: ``` salsa --user yadd push_repo ./test salsa --group js-team --kgb --irc-channel=devscripts push_repo . ``` - **rename\_branch** Rename branch given in **--source-branch** with name given in **--dest-branch**. You can use **--no-fail**, **--all** and **--all-archived** options here. - **search\_projects** or **search\_repo** or **search** Search for a project using given string. Shows name, owner ID and other information. ``` salsa search_projects devscripts salsa search_projects debian/devscripts salsa search_projects 18475 ``` - **update\_projects** or **update\_repo** Configure projects using parameters given to command line. A project name has to be given unless **--all** or **--all-archived** is set. Prefer to use **update\_safe**. ``` salsa --user yadd --tagpending --kgb --irc=devscripts update_projects test salsa --group js-team update_projects --all salsa --group js-team --rename-head update_projects test1 test2 test3 salsa update_projects js-team/node-mongodb --kgb --irc debian-js ``` By default when using **--all**, salsa will fail on first error. If you want to continue, set **--no-fail**. In this case, salsa will display a warning for each project that has fail but continue with next project. Then to see full errors, set **--verbose**. - **update\_safe** Launch **check\_projects** and ask before launching **update\_projects** (unless **--yes**). ``` salsa --user yadd --tagpending --kgb --irc=devscripts update_safe test salsa --group js-team update_safe --all salsa --group js-team --rename-head update_safe test1 test2 test3 salsa update_safe js-team/node-mongodb --kgb --irc debian-js ``` ### Other - **purge\_cache** Empty local cache. ## OPTIONS ### General options - **--chdir** or **-C** Change directory before launching command: ``` salsa --chdir ~/debian checkout debian/libapache2-mod-fcgid ``` - **--cache-file** File to store cached values. An empty value disables cache. Default: `"~/.cache/salsa.json"`. `".devscripts"` value: **SALSA\_CACHE\_FILE** - **--no-cache** Disable cache usage. Same as **--cache-file ''** - **--conf-file** or **--conffile** Add or replace default configuration files. This can only be used as the first option given on the command-line. Default: `"/etc/devscripts.conf"` and `"~/.devscripts"`. - replace: ``` salsa --conf-file test.conf ... salsa --conf-file test.conf --conf-file test2.conf ... ``` - add: ``` salsa --conf-file +test.conf ... salsa --conf-file +test.conf --conf-file +test2.conf ... ``` If one **--conf-file** has no `"+"`, default configuration files are ignored. - **--no-conf** or **--noconf** Don't read any configuration files. This can only be used as the first option given on the command-line. - **--debug** Enable debugging output. - **--group** Team to use. Use `"salsa search_groups name"` to find it. If you want to use a subgroup, you have to set its full path: ``` salsa --group perl-team/modules/packages check_projects lemonldap-ng ``` `".devscripts"` value: **SALSA\_GROUP** Be careful when you use **SALSA\_GROUP** in your `".devscripts"` file. Every **salsa** command will be executed in group space, for example if you want to propose a little change in a project using **salsa fork** + **salsa merge\_request**, this "fork" will be done in group space unless you set a **--user**/**--user-id**. Prefer to use an alias in your `".bashrc"` file. Example: ``` alias jsteam_admin="salsa --group js-team" ``` or ``` alias jsteam_admin="salsa --conf-file ~/.js.conf ``` or to use both .devscripts and .js.conf: ``` alias jsteam_admin="salsa --conf-file +~/.js.conf ``` then you can fix **SALSA\_GROUP** in `"~/.js.conf"` To enable bash completion for your alias, add this in your .bashrc file: ``` _completion_loader salsa complete -F _salsa_completion jsteam_admin ``` - **--group-id** Group ID to use. Use `"salsa search_groups name"` to find it. `".devscripts"` value: **SALSA\_GROUP\_ID** Be careful when you use **SALSA\_GROUP\_ID** in your `".devscripts"` file. Every **salsa** command will be executed in group space, for example if you want to propose a little change in a project using **salsa fork** + **salsa merge\_request**, this "fork" will be done in group space unless you set a **--user**/**--user-id**. Prefer to use an alias in your `".bashrc"` file. Example: ``` alias jsteam_admin="salsa --group-id 2666" ``` or ``` alias jsteam_admin="salsa --conf-file ~/.js.conf ``` then you can fix **SALSA\_GROUP\_ID** in `"~/.js.conf"`. - **--help** Displays this manpage. - **--info** or **-i** Prompt before sensible changes. `".devscripts"` value: **SALSA\_INFO** (yes/no) - **--path** Repository path. Default to group or user path. `".devscripts"` value: **SALSA\_REPO\_PATH** - **--token** Token value (see above). - **--token-file** File to find token (see above). - **--user** Username to use. If neither **--group**, **--group-id**, **--user** or **--user-id** is set, salsa uses current user ID (corresponding to salsa private token). - **--user-id** User ID to use. Use `"salsa search_users name"` to find one. If neither **--group**, **--group-id**, **--user** or **--user-id** is set, salsa uses current user ID (corresponding to salsa private token). `".devscripts"` value: **SALSA\_USER\_ID** - **--verbose** Enable verbose output. - **--yes** Never ask for consent. `".devscripts"` value: **SALSA\_YES** (yes/no) ### List/search project options - **--archived**, **--no-archived** Instead of looking to active projects, list or search in archived projects. Note that you can't have both archived and unarchived projects in the same request. Default: no *(ie --no-archived)*. `".devscripts"` value: **SALSA\_ARCHIVED** (yes/no) ### Update/create project options - **--all**, **--all-archived** When set, all projects of group/user are affected by command. **--all** will filter all active projects, whereas **--all-archived** will include active and archived projects. - **--skip**, **--no-skip** Ignore project with **--all** or **--all-achived**. Example: ``` salsa update_projects --tagpending --all --skip qa --skip devscripts ``` To set multiples values, use spaces. Example: ``` SALSA_SKIP=qa devscripts ``` Using **--no-skip** will ignore any projects to be skipped and include them. `".devscripts"` value: **SALSA\_SKIP** - **--skip-file** Ignore projects in this file (1 project per line). ``` salsa update_projects --tagpending --all --skip-file ~/.skip ``` `".devscripts"` value: **SALSA\_SKIP\_FILE** - **--build-timeout** The maximum amount of time, in seconds, that a job can run. Default: 3600 (60 minutes). ``` salsa update_safe myrepo --build-timeout 3600 ``` `".devscripts"` value: **SALSA\_BUILD\_TIMEOUT** - **--avatar-path** Path to an image for the project's avatar. If path value contains "%p", it is replaced by project name. `".devscripts"` value: **SALSA\_AVATAR\_PATH** - **--ci-config-path** Configure configuration file path of GitLab CI. Default: empty. Example: ``` salsa update_safe --ci-config-path recipes/debian.yml@salsa-ci-team/pipeline debian/devscripts ``` `".devscripts"` value: **SALSA\_CI\_CONFIG\_PATH** - **--desc**, **--no-desc** Configure a project's description using pattern given in **desc-pattern**. `".devscripts"` value: **SALSA\_DESC** (yes/no) - **--desc-pattern** Project's description pattern. "%p" is replaced by project's name, while "%P" is replaced by project's name given in command (may contains full path). Default: "Debian package `%p`". `".devscripts"` value: **SALSA\_DESC\_PATTERN** - **--email**, **--no-email**, **--disable-email** Enable, ignore or disable email-on-push. `".devscripts"` value: **SALSA\_EMAIL** (yes/ignore/no, default: ignore) - **--email-recipient** Email-on-push recipient. Can be multi valued: ``` $ salsa update_safe myrepo \ --email-recipient foo@foobar.org \ --email-recipient bar@foobar.org ``` If recipient value contains "%p", it is replaced by project name. `".devscripts"` value: **SALSA\_EMAIL\_RECIPIENTS** (use spaces to separate multiples recipients) - **--analytics** Set analytics feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_ANALYTICS** (yes/private/no, default: yes) - **--auto-devops** Set auto devops feature. `".devscripts"` value: **SALSA\_ENABLE\_AUTO\_DEVOPS** (yes/no, default: yes) - **--container** Set container feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_CONTAINER** (yes/private/no, default: yes) - **--environments** Set environments feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_ENVIRONMENTS** (yes/private/no, default: yes) - **--feature-flags** Set feature flags feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_FEATURE\_FLAGS** (yes/private/no, default: yes) - **--forks** Set forking a project feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_FORKS** (yes/private/no, default: yes) - **--infrastructure** Set infrastructure feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_INFRASTRUCTURE** (yes/private/no, default: yes) - **--issues** Set issues feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_ISSUES** (yes/private/no, default: yes) - **--jobs** Set jobs feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_JOBS** (yes/private/no, default: yes) - **--lfs** Set Large File Storage (LFS) feature. `".devscripts"` value: **SALSA\_ENABLE\_LFS** (yes/no, default: yes) - **--mr** Set merge requests feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_MR** (yes/private/no, default: yes) - **--monitor** Set monitor feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_MONITOR** (yes/private/no, default: yes) - **--packages** Set packages feature. `".devscripts"` value: **SALSA\_ENABLE\_PACKAGES** (yes/no, default: yes) - **--pages** Set pages feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_PAGES** (yes/private/no, default: yes) - **--releases** Set releases feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_RELEASES** (yes/private/no, default: yes) - **--enable-remove-source-branch**, **--disable-remove-source-branch** Enable or disable deleting source branch option by default for all new merge requests. `".devscripts"` value: **SALSA\_REMOVE\_SOURCE\_BRANCH** (yes/no, default: yes) - **--repo** Set the project's repository feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_REPO** (yes/private/no, default: yes) - **--request-access** Allow users to request member access. `".devscripts"` value: **SALSA\_REQUEST\_ACCESS** (yes/no) - **--requirements** Set requirements feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_REQUIREMENTS** (yes/private/no, default: yes) - **--security-compliance** Enable or disabled Security and Compliance feature. `".devscripts"` value: **SALSA\_ENABLE\_SECURITY\_COMPLIANCE** (yes/no) - **--service-desk** Allow service desk feature. `".devscripts"` value: **SALSA\_ENABLE\_SERVICE\_DESK** (yes/no) - **--snippets** Set snippets feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_SNIPPETS** (yes/private/no, default: yes) - **--wiki** Set wiki feature with permissions. `".devscripts"` value: **SALSA\_ENABLE\_WIKI** (yes/private/no, default: yes) - **--irc-channel** IRC channel for KGB or Irker. Can be used more than one time only with **--irker**. **Important**: channel must not include the first "#". If salsa finds a channel starting with "#", it will consider that the channel starts with 2 "#"! `".devscript"` value: **SALSA\_IRC\_CHANNEL** Multiple values must be space separated. Since configuration files are read using **sh**, be careful when using "#": you must enclose the channel with quotes, else **sh** will consider it as a comment and will ignore this value. - **--irker**, **--no-irker**, **--disable-irker** Enable, ignore or disable Irker service. `".devscripts"` value: **SALSA\_IRKER** (yes/ignore/no, default: ignore) - **--irker-host** Irker host. Default: ruprecht.snow-crash.org. `".devscripts"` value: **SALSA\_IRKER\_HOST** - **--irker-port** Irker port. Default: empty (default value). `".devscripts"` value: **SALSA\_IRKER\_PORT** - **--kgb**, **--no-kgb**, **--disable-kgb** Enable, ignore or disable KGB webhook. `".devscripts"` value: **SALSA\_KGB** (yes/ignore/no, default: ignore) - **--kgb-options** List of KGB enabled options (comma separated). Default: issues\_events, merge\_requests\_events, note\_events, pipeline\_events, push\_events, tag\_push\_events, wiki\_page\_events, enable\_ssl\_verification ``` $ salsa update_safe debian/devscripts --kgb --irc-channel devscripts \ --kgb-options 'merge_requests_events,issues_events,enable_ssl_verification' ``` List of available options: confidential\_comments\_events, confidential\_issues\_events, confidential\_note\_events, enable\_ssl\_verification, issues\_events, job\_events, merge\_requests\_events, note\_events, pipeline\_events, tag\_push\_events, wiki\_page\_events `".devscripts"` value: **SALSA\_KGB\_OPTIONS** - **--no-fail** Don't stop on error when using **update\_projects** with **--all** or **--all-archived** when set to yes. `".devscripts"` value: **SALSA\_NO\_FAIL** (yes/no, default: no) - **--rename-head**, **--no-rename-head** Rename HEAD branch given by **--source-branch** into **--dest-branch** and change "default branch" of project. Works only with **update\_projects**. `".devscripts"` value: **SALSA\_RENAME\_HEAD** (yes/no) - **--source-branch** Default: "master". `".devscripts"` value: **SALSA\_SOURCE\_BRANCH** - **--dest-branch** Default: "debian/latest". `".devscripts"` value: **SALSA\_DEST\_BRANCH** - **--tagpending**, **--no-tagpending**, **--disable-tagpending** Enable, ignore or disable "tagpending" webhook. `".devscripts"` value: **SALSA\_TAGPENDING** (yes/ignore/no, default: ignore) ### Pipeline schedules - **--schedule-desc** Description of the pipeline schedule. - **--schedule-ref** Branch or tag name that is triggered. - **--schedule-cron** Cron schedule. Example: ``` 0 1 * * *. ``` - **--schedule-tz** Time zone to run cron schedule. Default: UTC. - **--schedule-enable**, **--schedule-disable** Enable/disable the pipeline schedule to run. Default: disabled. - **--schedule-run** Trigger **--schedule-desc** scheduled pipeline to run immediately. Default: false. - **--schedule-delete** Delete **--schedule-desc** pipeline schedule. ### Merge requests options - **--mr-title** Title for merge request. Default: last commit title. - **--mr-desc** Description of new MR. Default: - empty if **--mr-title** is set - last commit description if any - **--mr-dst-branch** (or second command line argument) Destination branch. Default: "master". - **--mr-dst-project** (or first command line argument) Destination project. Default: project from which the current project was forked; or, if not found, "upstream" value found using **git remote --verbose show**; or using source project. If **--mr-dst-project** is set to **same**, salsa will use source project as destination. - **--mr-src-branch** Source branch. Default: current branch. - **--mr-src-project** Source project. Default: current project found using **git remote --verbose show**. - **--mr-allow-squash**, **--no-mr-allow-squash** Allow upstream project to squash your commits, this is the default. `".devscripts"` value: **SALSA\_MR\_ALLOW\_SQUASH** (yes/no) - **--mr-remove-source-branch**, **--no-mr-remove-source-branch** Remove source branch if merge request is accepted. Default: no. `".devscripts"` value: **SALSA\_MR\_REMOVE\_SOURCE\_BRANCH** (yes/no) ### Options to manage other GitLab instances - **--api-url** GitLab API. Default: \. `".devscripts"` value: **SALSA\_API\_URL** - **--git-server-url** Default: "git@salsa.debian.org:". `".devscripts"` value: **SALSA\_GIT\_SERVER\_URL** - **--irker-server-url** Default: "ircs://irc.oftc.net:6697/". `".devscripts"` value: **SALSA\_IRKER\_SERVER\_URL** - **--kgb-server-url** Default: \. `".devscripts"` value: **SALSA\_KGB\_SERVER\_URL** - **--tagpending-server-url** Default: \. `".devscripts"` value: **SALSA\_TAGPENDING\_SERVER\_URL** *Configuration file example* Example to use salsa with \ (group "lemonldap-ng"): ``` SALSA_TOKEN=`cat ~/.ow2-gitlab-token` SALSA_API_URL=https://gitlab.ow2.org/api/v4 SALSA_GIT_SERVER_URL=git@gitlab.ow2.org: SALSA_GROUP_ID=34 ``` Then to use it, add something like this in your `".bashrc"` file: ``` alias llng_admin='salsa --conffile ~/.salsa-ow2.conf' ``` ## SEE ALSO **dpt-salsa** ## AUTHOR Xavier Guimard \ ## COPYRIGHT AND LICENSE Copyright (C) 2018, Xavier Guimard \ It contains code formerly found in dpt-salsa *(pkg-perl-tools)* copyright 2018, gregor herrmann \. This library is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see \.