Skip to content

Conversation

@Gauvino
Copy link
Contributor

@Gauvino Gauvino commented Oct 31, 2025

Description

This PR continues the work from #2019 and #2111 by renaming additional "jellyseerr" references to "seerr" that were missed in previous refactors. Specifically:

  • Renamed the documentation folder from using-jellyseerr/advanced/ to using-seerr/advanced/
  • Updated internal documentation references and links to use the new path structure
  • Fixed broken links caused by the folder rename
  • Addressed remaining "jellyseerr" references throughout the codebase

Note: The majority of remaining "jellyseerr" references are in translation files managed by Weblate.

To-Dos

  • Disclosed any use of AI (see our policy)
  • Successful build pnpm build
  • Translation keys pnpm i18n:extract
  • Database migration (if required)

Issues Fixed or Closed

@gauthier-th
Copy link
Member

Did you see #2111?

@Gauvino Gauvino force-pushed the jellyseerr-to-seerr branch 2 times, most recently from ce3a4db to 7f77bb6 Compare October 31, 2025 15:48
@Gauvino
Copy link
Contributor Author

Gauvino commented Oct 31, 2025

Did you see #2111?

Yes I've seen it, I wanted to contribute by completing the few changes that were missing to complete the migration

Edit: Prettier is not happy because of the // Todo

@github-actions github-actions bot added the merge conflict Cannot merge due to merge conflicts label Nov 3, 2025
@github-actions
Copy link

github-actions bot commented Nov 3, 2025

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

@github-actions github-actions bot removed the merge conflict Cannot merge due to merge conflicts label Nov 3, 2025
@Gauvino Gauvino marked this pull request as ready for review November 3, 2025 21:34
@Gauvino Gauvino requested a review from a team as a code owner November 3, 2025 21:34
@Gauvino Gauvino force-pushed the jellyseerr-to-seerr branch from b56eca1 to daab5dc Compare November 8, 2025 13:36
Updates repository references, Docker image paths, and documentation links to reflect the new Seerr branding. Replaces fallenbagel/jellyseerr references with seerr-team/seerr throughout README, Helm charts, and documentation files.

Removes legacy Jellyseerr blog post and image assets, replacing them with Seerr equivalents. Adds TODO comments for pending package renames on Arch Linux and NixOS distributions.

Maintains backwards compatibility by preserving old package references in version checking components until external package repositories complete their renames.
@Gauvino Gauvino force-pushed the jellyseerr-to-seerr branch 2 times, most recently from c0b0588 to 7cd67f8 Compare November 8, 2025 13:40
@github-actions
Copy link

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

@github-actions github-actions bot added the merge conflict Cannot merge due to merge conflicts label Nov 14, 2025
@github-actions github-actions bot removed the merge conflict Cannot merge due to merge conflicts label Nov 14, 2025
…team

Updates repository URLs and translation service links to reflect the Seerr rebrand, replacing jellyseerr.dev references with seerr.dev and updating Docker Hub organization from seerr-team to seerr.

Adds six additional maintainers to the authors configuration (M0NsTeRRR, TheCatLady, sct, OwsleyJr, 0xSysR3ll, sudo-kraken) and includes them as co-authors on the welcome blog post.

Standardizes maintainer titles by removing "Co-" and "Developer" prefixes, establishing a consistent "Maintainer of Seerr" designation across all team members.
@Gauvino
Copy link
Contributor Author

Gauvino commented Nov 14, 2025

Is it good for you now ? @M0NsTeRRR and @gauthier-th ?

Updates documentation to reference the main branch instead of develop branch for build instructions, reflecting the current repository structure.

Enhances author profiles with real names, professional titles, email addresses, and expanded role descriptions to provide better context about maintainers.
Copy link
Contributor Author

@Gauvino Gauvino left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just made the authors.yml file with I think everyone in the seerr-team but need to make sure that all the information is correct, thanks in advance for the response!

Reverts author list to original Jellyseerr maintainers and updates their titles and descriptions to correctly reference Jellyseerr instead of Seerr.

Removes additional authors that were added during the Seerr fork, keeping only the two core original maintainers (fallenbagel and gauthier-th) to accurately represent the project's heritage.
Adds GitHub profile reference to the blog author configuration to enable proper social media linking and improve author profile completeness.
Copy link
Member

@gauthier-th gauthier-th left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@gauthier-th gauthier-th left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rename the docs/using-jellyseerr/ folder: here

@Gauvino
Copy link
Contributor Author

Gauvino commented Nov 18, 2025

Please rename the docs/using-jellyseerr/ folder: here

sorry that i missed that good now i think

also what do you do about the weblate of seerr cause it's still jellyseerr

and this branch could you rename it ?
image

@0xSysR3ll
Copy link
Contributor

0xSysR3ll commented Nov 18, 2025

Please rename the docs/using-jellyseerr/ folder: here

sorry that i missed that good now i think

also what do you do about the weblate of seerr cause it's still jellyseerr

and this branch could you rename it ?

image

Weblate translations will be taken care of, don't worry.

And the legacy-jellyseerr branch is for the old docs deployment that we are still using for now.

@Gauvino
Copy link
Contributor Author

Gauvino commented Nov 18, 2025

Please rename the docs/using-jellyseerr/ folder: here

sorry that i missed that good now i think

also what do you do about the weblate of seerr cause it's still jellyseerr

and this branch could you rename it ?

image

Weblate translations will be taken care of, don't worry.

And the legacy-jellyseerr branch is for the old docs deployment that we are still using for now.

Ok so i don't have to do anything more, maybe delete this workflow or something, cause one workflow use this branch

@0xSysR3ll
Copy link
Contributor

Please rename the docs/using-jellyseerr/ folder: here

sorry that i missed that good now i think
also what do you do about the weblate of seerr cause it's still jellyseerr
and this branch could you rename it ?
image

Weblate translations will be taken care of, don't worry.
And the legacy-jellyseerr branch is for the old docs deployment that we are still using for now.

Ok so i don't have to do anything more, maybe delete this workflow or something, cause one workflow use this branch

Nope. That's all for this PR thanks :)
I you could just rebase so that we can merge please.

@Gauvino
Copy link
Contributor Author

Gauvino commented Nov 18, 2025

Please rename the docs/using-jellyseerr/ folder: here

sorry that i missed that good now i think

also what do you do about the weblate of seerr cause it's still jellyseerr

and this branch could you rename it ?

image

Weblate translations will be taken care of, don't worry.

And the legacy-jellyseerr branch is for the old docs deployment that we are still using for now.

Ok so i don't have to do anything more, maybe delete this workflow or something, cause one workflow use this branch

Nope. That's all for this PR thanks :)

I you could just rebase so that we can merge please.

I could do that tomorrow morning no problem but is really necessary since you squash on merge ?

@M0NsTeRRR M0NsTeRRR enabled auto-merge (squash) November 18, 2025 21:48
@M0NsTeRRR M0NsTeRRR merged commit af083a3 into seerr-team:develop Nov 18, 2025
11 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants