starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

[PR #10334] #10333 Updates issue stale action to fix issues with not running #12438

New Issue
Closed
opened 2026-02-07 06:55:53 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-07 06:55:53 +03:00
Owner
Copy Link

Original Pull Request: https://github.com/jellyfin/jellyfin/pull/10334

State: closed
Merged: Yes

GitHub actions are difficult to test locally, so I'm making some educated guesses about why the stale action was not running correctly. It looks like the primary culprit is that the action is not caching state and is subsequently starting with the most recent issue/PR and never getting past the first 75 as described in this issue. A view of the action logs corroberates this.

Changes

  • Adds the actions: write permission to enable writing to the cache to maintain state
  • Updates the cron to run twice daily instead of once
  • Updates the verbiage on the stale-issue-message to be more concise
  • Updates the link for getting help
  • Adds a close-issue-message

Issues
#10333

**Original Pull Request:** https://github.com/jellyfin/jellyfin/pull/10334 **State:** closed **Merged:** Yes --- GitHub actions are difficult to test locally, so I'm making some educated guesses about why the stale action was not running correctly. It looks like the primary culprit is that the action is not caching state and is subsequently starting with the most recent issue/PR and never getting past the first 75 as described in [this issue](https://github.com/actions/stale/issues/1090#issuecomment-1710940734). A view of the action logs corroberates this. **Changes** - Adds the `actions: write` permission to enable writing to the cache to maintain state - Updates the `cron` to run twice daily instead of once - Updates the verbiage on the `stale-issue-message` to be more concise - Updates the link for getting help - Adds a `close-issue-message` **Issues** #10333
OVERLORD added the pull-request label 2026-02-07 06:55:53 +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#12438
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?