Skip to content

Fix Jellyfin to use path-specific scanning instead of full library refresh #7

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pukabyte merged 1 commit into from
Jan 23, 2026

Fix Jellyfin to use path-specific scanning instead of full library re…

268458e
Select commit
Loading
Failed to load commit list.
Merged

Fix Jellyfin to use path-specific scanning instead of full library refresh #7

Fix Jellyfin to use path-specific scanning instead of full library re…
268458e
Select commit
Loading
Failed to load commit list.
GitGuardian / GitGuardian Security Checks succeeded Jan 23, 2026 in 31s

No secrets detected ✅

1 commit was scanned without uncovering any secrets.

Details

Commit scanned: 1

  • Pull request #7: fix/jellyfin-path-specific-scan 👉 main

🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

View more details on GitGuardian