Donkie 348499f469 Tag issues opened by sponsors ...

The Supporter tier promises that issues a sponsor opens get an exclusive tag
so they surface first.

The sponsorship lookup is viewer-relative, so it runs on the PAT rather than
GITHUB_TOKEN, whose viewer is the Actions bot that nobody sponsors. Reading
privacyLevel needs that token's read:user scope.

Private sponsors are skipped. The label is public and applying it would
disclose a sponsorship they chose to keep hidden.

2026-09-02 17:59:16 +02:00

..

apidocs.yml

CI fixes

2026-01-18 16:55:31 +01:00

ci.yml

Build on Node 24, which is not end-of-life

2026-07-31 09:00:16 +02:00

guard-translations.yml

fix(ci): diff PRs from the merge base in guard-translations

2026-08-01 22:11:42 +02:00

issue-manager.yml

ci: bump issue-manager to 0.8.1 and fix waiting delay

2026-07-24 10:22:08 +02:00

sponsor-label.yml

Tag issues opened by sponsors

2026-09-02 17:59:16 +02:00

sponsors.yml

Push the sponsors image with the PAT

2026-09-01 22:32:29 +02:00

trigger-release.yml

Build on Node 24, which is not end-of-life

2026-07-31 09:00:16 +02:00

weblate-automerge.yml

ci: merge Weblate PRs instead of squashing them

2026-08-05 18:36:16 +02:00