A question of curiosity: when I push a commit to salsa with a "Closes:
#nnnnn" in the changelog, the BTS gets a "tag: pending" notification.
I looked and looked, and could not find out how salsa does this?
Could anyone enlighten me? (The standard debian-ci scripts, which the repositories use for their CI, appear to only do something with RC
bugs.)

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Julian (2022.08.14_07:18:49_+0000)

A question of curiosity: when I push a commit to salsa with a "Closes: #nnnnn" in the changelog, the BTS gets a "tag: pending" notification.
I looked and looked, and could not find out how salsa does this?
Could anyone enlighten me? (The standard debian-ci scripts, which the repositories use for their CI, appear to only do something with RC
bugs.)

It's a salsa webhook: https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages

We don't have tooling that automatically configures all the repos, but
when we migrated to salsa, we set them all up for tagpending, and
posting to #debian-python-changes on IRC

SR

--
Stefano Rivera
http://tumbleweed.org.za/
+1 415 683 3272

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, Aug 14, 2022 at 08:45:32AM +0000, Stefano Rivera wrote:

Hi Julian (2022.08.14_07:18:49_+0000)

A question of curiosity: when I push a commit to salsa with a "Closes: #nnnnn" in the changelog, the BTS gets a "tag: pending" notification.
I looked and looked, and could not find out how salsa does this?
Could anyone enlighten me? (The standard debian-ci scripts, which the repositories use for their CI, appear to only do something with RC
bugs.)

It's a salsa webhook: https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages

We don't have tooling that automatically configures all the repos, but
when we migrated to salsa, we set them all up for tagpending, and
posting to #debian-python-changes on IRC

Ah, super, thanks! I'll start adding those to the projects I've
created.

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

It's a salsa webhook: https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages

We don't have tooling that automatically configures all the repos, but
when we migrated to salsa, we set them all up for tagpending, and
posting to #debian-python-changes on IRC

shameless plug, i fixed most of the packages in our repo to have the
proper wehbooks using https://github.com/sandrotosi/dpt-repos-check/blob/main/dpt-fix-integrations-webhooks.py
(and now automation is available in pypi2deb, when you let it create
the repo on salsa) -- consider new packages wont get the right setup
old webhooks, etc

I should probably run it more periodically

--
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, Aug 14, 2022 at 11:38:10AM -0400, Sandro Tosi wrote:

It's a salsa webhook: https://wiki.debian.org/Salsa/Doc#Dealing_with_Debian_BTS_from_commit_messages

We don't have tooling that automatically configures all the repos, but
when we migrated to salsa, we set them all up for tagpending, and
posting to #debian-python-changes on IRC

shameless plug, i fixed most of the packages in our repo to have the
proper wehbooks using https://github.com/sandrotosi/dpt-repos-check/blob/main/dpt-fix-integrations-webhooks.py
(and now automation is available in pypi2deb, when you let it create
the repo on salsa) -- consider new packages wont get the right setup
old webhooks, etc

I should probably run it more periodically

Oh wow, that's awesome, thanks!!

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)