Henrik Rydgård c93f7d2152 Github CI: Use pull_request_target instead of pull_request ...

The idea is that PRs should build on CI even if there are conflicts.

This is useful for hotfix branches like v1.19.3-commits, where I
cherry-pick PRs from master to produce a new release without including
any risky recent changes.

I'm testing it in that branch right now and it seems to work. I'm making
this a separate PR before including in the main branch, so you guys can
warn me in case this is a mistake somehow :)

I showed my changes to ChatGPT and it suggested adding the permissions
clause, not exactly sure why it's more needed now.

Discussion here: https://github.com/orgs/community/discussions/26304

2025-07-14 08:37:01 +02:00

..

appimage.yml

Github CI: Use pull_request_target instead of pull_request

2025-07-14 08:37:01 +02:00

build.yml

Github CI: Use pull_request_target instead of pull_request

2025-07-14 08:37:01 +02:00

generateDockerLayer.yml

CI: Simplify docker workflow

2025-06-08 12:46:24 -04:00

manual_generate_apk.yml

CI: Simplify some conditions and other small cleanups

2025-06-08 12:50:02 -04:00

manual_generate_ipa.yml

install dependencies

2025-06-22 19:13:20 +07:00

manual_generate_uwp.yml

CI: Simplify some conditions and other small cleanups

2025-06-08 12:50:02 -04:00

tarball.yml

Bump softprops/action-gh-release from 2.2.2 to 2.3.2

2025-07-01 10:18:51 +00:00