<feed xmlns='http://www.w3.org/2005/Atom'>
<title>staging/stintel/.github/issue-labeller.yml, branch master</title>
<subtitle>Staging tree of Stijn Tintel</subtitle>
<id>https://git.openwrt.org/openwrt/staging/stintel/atom?h=master</id>
<link rel='self' href='https://git.openwrt.org/openwrt/staging/stintel/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/stintel/'/>
<updated>2026-07-25T09:24:31Z</updated>
<entry>
<title>github: switch issue-labeller to bot webhook and add configuration</title>
<updated>2026-07-25T09:24:31Z</updated>
<author>
<name>Josef Schlehofer</name>
</author>
<published>2026-07-23T09:27:39Z</published>
<link rel='alternate' type='text/html' href='https://git.openwrt.org/openwrt/staging/stintel/commit/?id=69668f8f828b94a7d9fd908bf82d24e5a2a13d48'/>
<id>urn:sha1:69668f8f828b94a7d9fd908bf82d24e5a2a13d48</id>
<content type='text'>
Remove the standalone GitHub Actions issue-labeller.yml workflow in favor
of the webhook-based openwrt-bot worker.

Enable issue labeller in formalities.json and add a declarative
.github/issue-labeller.yml configuration file for automated validation
and labelling of bug reports (release, target, image kind, device).

The release rule lists two alternative conditions under a single label
key: concrete releases (x.y.z, x.y.z-rcN) are validated against their
Git tag via exists check, while stable-branch snapshots (x.y-SNAPSHOT)
are format-validated only — OpenWrt does not tag snapshot builds.

Signed-off-by: Josef Schlehofer &lt;pepe.schlehofer@gmail.com&gt;
Link: https://github.com/openwrt/openwrt/pull/24382
Signed-off-by: Christian Marangi &lt;ansuelsmth@gmail.com&gt;
</content>
</entry>
</feed>
