Idea: sign pull requests' builds only for the ones a maintainer let through #378
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#378
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The idea
CI keeps building every pull request that is not a draft, but
pr-publish.ymlsigns and publishes only those with thetesting wantedlabel or whose author may push to Longshot (the rule test requests follow).Why: once the pull request key exists, any non-draft pull request from anyone gets a signed build in Longshot's own releases. The launcher warns, and shows testing wanted first, but the signature still vouches for code nobody looked at. The code review of #353 ranked this its top risk.
Note: Forgejo answers
collaborators/{user}/permissiononly to repo admins, so the job's token cannot ask it; the label alone, or a list of maintainers, may be what works.Anything else
A follow-up of #337 (testing pull requests from the launcher): CI in #353, the launcher's picker in LongshotLauncher pull request 59.
gab9281 referenced this issue2026-11-14 06:49:51 +00:00
Opened by mistake: its idea is now a follow-up in the list on #337. Closing; a maintainer may delete it.