starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Overseerr: Installs development branch of the app #61

New Issue
Closed
opened 2026-02-04 16:24:30 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 16:24:30 +03:00
Owner
Copy Link

Originally created by @ThisIsJeron on GitHub (Nov 18, 2024).

Originally assigned to: @newzealandpaul on GitHub.

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

After using default settings for overseerr, I am seeing within settings that it installs the development branch. I think it is best that it installs a release branch and not a development branch

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @ThisIsJeron on GitHub (Nov 18, 2024). Originally assigned to: @newzealandpaul on GitHub. ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. After using default settings for overseerr, I am seeing within settings that it installs the development branch. I think it is best that it installs a release branch and not a development branch ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
OVERLORD added the enhancement label 2026-02-04 16:24:30 +03:00
OVERLORD commented 2026-02-04 16:24:41 +03:00
Author
Owner
Copy Link

@newzealandpaul commented on GitHub (Nov 18, 2024):

Yes, you are correct it installs the main branch, and when updated, it simply pulls from the main branch. I think making it use a release would be a good idea. I will have a go at changing it.

@newzealandpaul commented on GitHub (Nov 18, 2024): Yes, you are correct it installs the main branch, and when updated, it simply pulls from the main branch. I think making it use a release would be a good idea. I will have a go at changing it.
OVERLORD commented 2026-02-04 16:24:51 +03:00
Author
Owner
Copy Link

@lichenophile commented on GitHub (Nov 21, 2024):

Jellyseerr shares this same scenario too

@lichenophile commented on GitHub (Nov 21, 2024): Jellyseerr shares this same scenario too
OVERLORD commented 2026-02-04 16:24:57 +03:00
Author
Owner
Copy Link

@j-cadena1 commented on GitHub (Dec 28, 2024):

I am also seeing that behaviour. The last update to the develop branch on my install shows that it was over 500 days ago. Is the project still alive I wonder...

@j-cadena1 commented on GitHub (Dec 28, 2024): I am also seeing that behaviour. The last update to the develop branch on my install shows that it was over 500 days ago. Is the project still alive I wonder...
OVERLORD commented 2026-02-04 16:25:03 +03:00
Author
Owner
Copy Link

@oOStroudyOo commented on GitHub (Dec 29, 2024):

Yes, it looks like Develop is their default branch. Last commit was 2 months ago.
Master, last updated July 28th 2023.

This seems more like a poorly run Overseerr repo, rather than a helper-script issue.
The helper-script currently clones the repo, which I believe by default will pull the repos default branch.

I guess this is up to the community here, would you rather pull the master last updated 17 months ago.
Or pull their "default" branch which is Develop?

Jellyseerr is a fork of overseerr which is why we see the same behavior here. However both branches are still active on Jellyseerr so we could specific main branch instead of default (develop).

@oOStroudyOo commented on GitHub (Dec 29, 2024): Yes, it looks like Develop is their default branch. Last commit was 2 months ago. Master, last updated July 28th 2023. This seems more like a poorly run Overseerr repo, rather than a helper-script issue. The helper-script currently clones the repo, which I believe by default will pull the repos default branch. I guess this is up to the community here, would you rather pull the master last updated 17 months ago. Or pull their "default" branch which is Develop? Jellyseerr is a fork of overseerr which is why we see the same behavior here. However both branches are still active on Jellyseerr so we could specific main branch instead of default (develop).
OVERLORD commented 2026-02-04 16:25:11 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 29, 2024):

Yep. It is actually the intention of the scripts to use the develop branch, as master/main has not been maintained there for ages, or only rarely.

@MickLesk commented on GitHub (Dec 29, 2024): Yep. It is actually the intention of the scripts to use the develop branch, as master/main has not been maintained there for ages, or only rarely.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label enhancement
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/ProxmoxVE#61
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?