starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-07-16 05:43:54 +03:00
Code Issues 822 Packages Projects Releases 17 Wiki Activity

[PR #16162] ci: use workflow_run pattern for PR workflows #14546

New Issue
Open
opened 2026-02-07 07:31:33 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 07:31:33 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/jellyfin/jellyfin/pull/16162
Author: @andrewrabert
Created: 2/1/2026
Status: 🔄 Open

Base: master ← Head: fix/ci-workflow-refactor

📝 Commits (1)

  • 3d0b84c ci: use workflow_run pattern for PR workflows

📊 Changes

4 files changed (+138 additions, -125 deletions)

View changed files

➕ .github/workflows/ci-compat-build.yml (+55 -0)
📝 .github/workflows/ci-compat.yml (+14 -77)
➕ .github/workflows/ci-openapi-build.yml (+55 -0)
📝 .github/workflows/ci-openapi.yml (+14 -48)

📄 Description

Summary

Refactor CI workflows to use the workflow_run pattern for PR builds.

Changes

  • Build jobs run on pull_request trigger with minimal permissions
  • Deploy/privileged jobs run on workflow_run, consuming artifacts
  • No functional changes to build or deploy behavior

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/jellyfin/jellyfin/pull/16162 **Author:** [@andrewrabert](https://github.com/andrewrabert) **Created:** 2/1/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `fix/ci-workflow-refactor` --- ### 📝 Commits (1) - [`3d0b84c`](https://github.com/jellyfin/jellyfin/commit/3d0b84ce48dba123b31f5754b765a9fdf5df3862) ci: use workflow_run pattern for PR workflows ### 📊 Changes **4 files changed** (+138 additions, -125 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/ci-compat-build.yml` (+55 -0) 📝 `.github/workflows/ci-compat.yml` (+14 -77) ➕ `.github/workflows/ci-openapi-build.yml` (+55 -0) 📝 `.github/workflows/ci-openapi.yml` (+14 -48) </details> ### 📄 Description ## Summary Refactor CI workflows to use the `workflow_run` pattern for PR builds. ## Changes - Build jobs run on `pull_request` trigger with minimal permissions - Deploy/privileged jobs run on `workflow_run`, consuming artifacts - No functional changes to build or deploy behavior --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-07 07:31:33 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#14546
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?