Debian Wiki - User contributions [en]

Salsa

2025-08-19T16:42:18Z

Otto: Clarify the merge-requests namespace is read-only

'''{{MediaWiki:Sitenotice}}'''

This page was mainly made to test Mediawiki for documenting a specific use case with screenshots, and can be deleted at any time.

=== Subscribe to email notifications about new Merge Requests in your project ===
[[File:Salsa notification settings example.png|alt=Screenshot of notification settings drop-down in Salsa|thumb|Notification settings drop-down in Salsa]]
By default, a new Merge Request on Salsa does not trigger an email notification to the project owner, as Salsa does not have any integration that would allow it to know which projects are Debian packages, and who are the maintainers. Therefore, each maintainer needs to manually ensure they are subscribed to email notifications for the Salsa projects of packages they maintain.

To do this, simply open the project main page, press on the bell icon, and select notification level ''Watch.''

To see a list of all projects subscribed, see the user settings page https://salsa.debian.org/-/profile/notifications.

=== Checking Merge Requests from the command-line ===
It is also possible to list all open Merge Requests using the [https://manpages.debian.org/unstable/devscripts/salsa.1.en.html salsa] tool from the <code>devscripts</code> package.

Example:
# salsa merge_requests debian/openssl
debian/openssl
Id : 81447
Title : Enable Salsa CI using default template
Author: otto
Status: can_be_merged
Url : <nowiki>https://salsa.debian.org/debian/openssl/-/merge_requests/11</nowiki>
There are also other command-line clients for GitLab, such as [https://manpages.debian.org/unstable/glab/glab.1.en.html glab]:
# glab mr list --repo debian/openssl
Showing 1 open merge request on debian/openssl. (Page 1)

!11 debian/openssl!11 Enable Salsa CI using default template (debian/unstable) ← (salsa-ci)
Third option is to use the special GitLab read-only <code>merge-request</code> namespace and fetch it:
# tail .git/config
[remote "merge-requests"]
url = git@salsa.debian.org:<project>.git
fetch = +refs/merge-requests/*/head:refs/remotes/merge-requests/*
tagopt = --no-tags

# git fetch merge-requests
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Total 4 (delta 3), reused 4 (delta 3), pack-reused 0 (from 0)
Unpacking objects: 100% (4/4), 374 bytes | 62.00 KiB/s, done.
From salsa.debian.org:<project>
* [new ref] refs/merge-requests/27/head -> merge-requests/27
* [new ref] refs/merge-requests/28/head -> merge-requests/28
* [new ref] refs/merge-requests/29/head -> merge-requests/29

=== Merge Requests on developer dashboards ===
Debian Developers and Maintainers should be checking the health of their packages regularly. There are two dashboards that give a good overview of the package health, and they both include a field indicating if there are open Merge Requests.

The [https://udd.debian.org/dmd/ UDD Maintainer dashboard] has a column for Salsa with the open MR count included:
[[File:UDD Salsa column screenshot.png|alt=UDD Salsa column screenshot|center|thumb]]

The [https://qa.debian.org/developer.php Screenshot of Debian Developer's Packages Overview] has a column for VCS information, where the open MR count shows as a exclamation mark and a number:
[[File:Screenshot of Debian Developer's Packages Overview VCS column.png|alt=Screenshot of Debian Developer's Packages Overview VCS column|center|thumb]]For individual packages you can also see the number of open Merge Requests on the Debian Tracker page:
[[File:Debian Tracker showing open Merge Requests.png|alt=Screenshot of Debian Tracker showing open Merge Requests|center|thumb]]

Salsa

2025-08-19T16:40:32Z

Otto: Include screenshot from Debian Tracker

'''{{MediaWiki:Sitenotice}}'''

This page was mainly made to test Mediawiki for documenting a specific use case with screenshots, and can be deleted at any time.

=== Subscribe to email notifications about new Merge Requests in your project ===
[[File:Salsa notification settings example.png|alt=Screenshot of notification settings drop-down in Salsa|thumb|Notification settings drop-down in Salsa]]
By default, a new Merge Request on Salsa does not trigger an email notification to the project owner, as Salsa does not have any integration that would allow it to know which projects are Debian packages, and who are the maintainers. Therefore, each maintainer needs to manually ensure they are subscribed to email notifications for the Salsa projects of packages they maintain.

To do this, simply open the project main page, press on the bell icon, and select notification level ''Watch.''

To see a list of all projects subscribed, see the user settings page https://salsa.debian.org/-/profile/notifications.

=== Checking Merge Requests from the command-line ===
It is also possible to list all open Merge Requests using the [https://manpages.debian.org/unstable/devscripts/salsa.1.en.html salsa] tool from the <code>devscripts</code> package.

Example:
# salsa merge_requests debian/openssl
debian/openssl
Id : 81447
Title : Enable Salsa CI using default template
Author: otto
Status: can_be_merged
Url : <nowiki>https://salsa.debian.org/debian/openssl/-/merge_requests/11</nowiki>
There are also other command-line clients for GitLab, such as [https://manpages.debian.org/unstable/glab/glab.1.en.html glab]:
# glab mr list --repo debian/openssl
Showing 1 open merge request on debian/openssl. (Page 1)

!11 debian/openssl!11 Enable Salsa CI using default template (debian/unstable) ← (salsa-ci)
Third option is to use the special GitLab merge-request namespace and fetch it:
# tail .git/config
[remote "merge-requests"]
url = git@salsa.debian.org:<project>.git
fetch = +refs/merge-requests/*/head:refs/remotes/merge-requests/*
tagopt = --no-tags

# git fetch merge-requests
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Total 4 (delta 3), reused 4 (delta 3), pack-reused 0 (from 0)
Unpacking objects: 100% (4/4), 374 bytes | 62.00 KiB/s, done.
From salsa.debian.org:<project>
* [new ref] refs/merge-requests/27/head -> merge-requests/27
* [new ref] refs/merge-requests/28/head -> merge-requests/28
* [new ref] refs/merge-requests/29/head -> merge-requests/29

=== Merge Requests on developer dashboards ===
Debian Developers and Maintainers should be checking the health of their packages regularly. There are two dashboards that give a good overview of the package health, and they both include a field indicating if there are open Merge Requests.

The [https://udd.debian.org/dmd/ UDD Maintainer dashboard] has a column for Salsa with the open MR count included:
[[File:UDD Salsa column screenshot.png|alt=UDD Salsa column screenshot|center|thumb]]

The [https://qa.debian.org/developer.php Screenshot of Debian Developer's Packages Overview] has a column for VCS information, where the open MR count shows as a exclamation mark and a number:
[[File:Screenshot of Debian Developer's Packages Overview VCS column.png|alt=Screenshot of Debian Developer's Packages Overview VCS column|center|thumb]]For individual packages you can also see the number of open Merge Requests on the Debian Tracker page:
[[File:Debian Tracker showing open Merge Requests.png|alt=Screenshot of Debian Tracker showing open Merge Requests|center|thumb]]

File:Debian Tracker showing open Merge Requests.png

2025-08-19T16:39:56Z

Otto:

Debian Tracker showing open Merge Requests

Salsa

2025-08-18T20:07:02Z

Otto: Include merge-requests namespace example

'''{{MediaWiki:Sitenotice}}'''

This page was mainly made to test Mediawiki for documenting a specific use case with screenshots, and can be deleted at any time.

=== Subscribe to email notifications about new Merge Requests in your project ===
[[File:Salsa notification settings example.png|alt=Screenshot of notification settings drop-down in Salsa|thumb|Notification settings drop-down in Salsa]]
By default, a new Merge Request on Salsa does not trigger an email notification to the project owner, as Salsa does not have any integration that would allow it to know which projects are Debian packages, and who are the maintainers. Therefore, each maintainer needs to manually ensure they are subscribed to email notifications for the Salsa projects of packages they maintain.

To do this, simply open the project main page, press on the bell icon, and select notification level ''Watch.''

To see a list of all projects subscribed, see the user settings page https://salsa.debian.org/-/profile/notifications.

=== Checking Merge Requests from the command-line ===
It is also possible to list all open Merge Requests using the [https://manpages.debian.org/unstable/devscripts/salsa.1.en.html salsa] tool from the <code>devscripts</code> package.

Example:
# salsa merge_requests debian/openssl
debian/openssl
Id : 81447
Title : Enable Salsa CI using default template
Author: otto
Status: can_be_merged
Url : <nowiki>https://salsa.debian.org/debian/openssl/-/merge_requests/11</nowiki>
There are also other command-line clients for GitLab, such as [https://manpages.debian.org/unstable/glab/glab.1.en.html glab]:
# glab mr list --repo debian/openssl
Showing 1 open merge request on debian/openssl. (Page 1)

!11 debian/openssl!11 Enable Salsa CI using default template (debian/unstable) ← (salsa-ci)
Third option is to use the special GitLab merge-request namespace and fetch it:
# tail .git/config
[remote "merge-requests"]
url = git@salsa.debian.org:<project>.git
fetch = +refs/merge-requests/*/head:refs/remotes/merge-requests/*
tagopt = --no-tags

# git fetch merge-requests
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Total 4 (delta 3), reused 4 (delta 3), pack-reused 0 (from 0)
Unpacking objects: 100% (4/4), 374 bytes | 62.00 KiB/s, done.
From salsa.debian.org:<project>
* [new ref] refs/merge-requests/27/head -> merge-requests/27
* [new ref] refs/merge-requests/28/head -> merge-requests/28
* [new ref] refs/merge-requests/29/head -> merge-requests/29

=== Merge Requests on developer dashboards ===
Debian Developers and Maintainers should be checking the health of their packages regularly. There are two dashboards that give a good overview of the package health, and they both include a field indicating if there are open Merge Requests.

The [https://udd.debian.org/dmd/ UDD Maintainer dashboard] has a column for Salsa with the open MR count included:
[[File:UDD Salsa column screenshot.png|alt=UDD Salsa column screenshot|center|thumb]]

The [https://qa.debian.org/developer.php Screenshot of Debian Developer's Packages Overview] has a column for VCS information, where the open MR count shows as a exclamation mark and a number:
[[File:Screenshot of Debian Developer's Packages Overview VCS column.png|alt=Screenshot of Debian Developer's Packages Overview VCS column|center|thumb]]

Salsa

2025-08-14T19:34:25Z

Otto: Show more examples

'''{{MediaWiki:Sitenotice}}'''

This page was mainly made to test Mediawiki for documenting a specific use case with screenshots, and can be deleted at any time.

=== Subscribe to email notifications about new Merge Requests in your project ===
[[File:Salsa notification settings example.png|alt=Screenshot of notification settings drop-down in Salsa|thumb|Notification settings drop-down in Salsa]]
By default, a new Merge Request on Salsa does not trigger an email notification to the project owner, as Salsa does not have any integration that would allow it to know which projects are Debian packages, and who are the maintainers. Therefore, each maintainer needs to manually ensure they are subscribed to email notifications for the Salsa projects of packages they maintain.

To do this, simply open the project main page, press on the bell icon, and select notification level ''Watch.''

To see a list of all projects subscribed, see the user settings page https://salsa.debian.org/-/profile/notifications.

=== Checking Merge Requests from the command-line ===
It is also possible to list all open Merge Requests using the [https://manpages.debian.org/unstable/devscripts/salsa.1.en.html salsa] tool from the <code>devscripts</code> package.

Example:
# salsa merge_requests debian/openssl
debian/openssl
Id : 81447
Title : Enable Salsa CI using default template
Author: otto
Status: can_be_merged
Url : <nowiki>https://salsa.debian.org/debian/openssl/-/merge_requests/11</nowiki>
There are also other command-line clients for GitLab, such as [https://manpages.debian.org/unstable/glab/glab.1.en.html glab]:
# glab mr list --repo debian/openssl
Showing 1 open merge request on debian/openssl. (Page 1)

!11 debian/openssl!11 Enable Salsa CI using default template (debian/unstable) ← (salsa-ci)

=== Merge Requests on developer dashboards ===
Debian Developers and Maintainers should be checking the health of their packages regularly. There are two dashboards that give a good overview of the package health, and they both include a field indicating if there are open Merge Requests.

The [https://udd.debian.org/dmd/ UDD Maintainer dashboard] has a column for Salsa with the open MR count included:
[[File:UDD Salsa column screenshot.png|alt=UDD Salsa column screenshot|center|thumb]]

The [https://qa.debian.org/developer.php Screenshot of Debian Developer's Packages Overview] has a column for VCS information, where the open MR count shows as a exclamation mark and a number:
[[File:Screenshot of Debian Developer's Packages Overview VCS column.png|alt=Screenshot of Debian Developer's Packages Overview VCS column|center|thumb]]

File:Screenshot of Debian Developer's Packages Overview VCS column.png

2025-08-14T19:30:15Z

Otto:

Screenshot of Debian Developer's Packages Overview VCS column

File:UDD Salsa column screenshot.png

2025-08-14T19:28:16Z

Otto:

UDD Salsa column screenshot

Salsa

2025-08-14T17:50:02Z

Otto: Testing creation of new page

File:Salsa notification settings example.png

2025-08-14T17:46:31Z

Otto:

Screenshot from Salsa

User:Otto

2025-07-20T15:44:44Z

Otto: Add my own profile page as a test of the new wiki

Debian Developer since 2015 - see https://contributors.debian.org/contributor/otto/

Personal blog at https://optimizedbyotto.com/