You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read a forum from like 2021 about linuxserver not wanting to support Jellyseerr. I am considering on forking this overseerr project and refactoring it to use jellyseerr.
I wonder if I give access to the forked repository if it's possible to then support Jellyseerr since the skeleton work should be cut out and it literally functions mostly like Overseerr since it's a fork from overseerr.
Reason for change
Linuxserver has the best maintained docker containers and I would like to continue to stay in this ecosystem since Overseerr is already supported and I am simply wanting Emby (Jellyseerr) support.
Proposed code change
I can fork the code, refactor, test, and share the repository with you?
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is this a new feature request?
Wanted change
I read a forum from like 2021 about linuxserver not wanting to support Jellyseerr. I am considering on forking this overseerr project and refactoring it to use jellyseerr.
I wonder if I give access to the forked repository if it's possible to then support Jellyseerr since the skeleton work should be cut out and it literally functions mostly like Overseerr since it's a fork from overseerr.
Reason for change
Linuxserver has the best maintained docker containers and I would like to continue to stay in this ecosystem since Overseerr is already supported and I am simply wanting Emby (Jellyseerr) support.
Proposed code change
I can fork the code, refactor, test, and share the repository with you?
The text was updated successfully, but these errors were encountered: