starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-26 00:05:58 +03:00

[GH-ISSUE #3048] [Feature Request]: Disable auto-updater for non-main branches #961

New issue

Closed

opened 2026-02-27 21:09:11 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 21:09:11 +03:00

Owner

Originally created by @shinra-electric on GitHub (Jun 7, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3048

Checklist

I have searched for a similar issue in this repository and did not find one.

Description

Turn off auto-update if the branch is not main.

Reason

When testing PRs or other branches, shad will ask to update the app to the latest main release. Accidentally selecting to update will overwrite the version that I'm trying to test, and the popup is annoying.

Turning off auto-update is not preferable, as I want to keep this turned on for the main branch.

There isn't any reason that I can think of for auto-updating PRs to main.

Examples

No response

Originally created by @shinra-electric on GitHub (Jun 7, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3048 ### Checklist - [x] I have searched for a similar issue in this repository and did not find one. ### Description Turn off auto-update if the branch is not main. ### Reason When testing PRs or other branches, shad will ask to update the app to the latest main release. Accidentally selecting to update will overwrite the version that I'm trying to test, and the popup is annoying. Turning off auto-update is not preferable, as I want to keep this turned on for the main branch. There isn't any reason that I can think of for auto-updating PRs to main. ### Examples _No response_

kerem closed this issue

2026-02-27 21:09:11 +03:00

kerem commented

2026-02-27 21:09:12 +03:00

Author

Owner

@diegolix29 commented on GitHub (Jun 7, 2025):

Bro just turn off automatic updates ezpz

@diegolix29 commented on GitHub (Jun 7, 2025): Bro just turn off automatic updates ezpz

kerem commented

2026-02-27 21:09:12 +03:00

Author

Owner

@diegolix29 commented on GitHub (Jun 7, 2025):

U can have user folder under ur pr testing folder and set auto update to off in that one so ur main will pick up ur global settings

@diegolix29 commented on GitHub (Jun 7, 2025): U can have user folder under ur pr testing folder and set auto update to off in that one so ur main will pick up ur global settings

kerem commented

2026-02-27 21:09:12 +03:00

Author

Owner

@GHU7924 commented on GitHub (Jun 7, 2025):

Turning off auto-update is not preferable, as I want to keep this turned on for the main branch.
There isn't any reason that I can think of for auto-updating PRs to main.

I completely agree.

Bro just turn off automatic updates ezpz

I did it, but it's a half-measure. It's not hard, but it's such an annoying choice, either you'll be constantly bothered by the update window for test PRs, or manually search for updates for the main branch, where I prefer to have automatic updates to the latest version of the emulator.

U can have user folder under ur pr testing folder and set auto update to off in that one so ur main will pick up ur global settings

That's the problem. You, as a person who is directly involved in development, may not notice this, but we, as regular users from the outside, are forced to finish something to help with testing.

We have to re-upload every new commit if there were edits that need to be double-checked to make sure the PR is moving in the right direction and there are no regressions.
These commits take their settings from the global settings, i.e. config.toml, so if you have auto-update enabled, then every time you run a new test build you are ALWAYS prompted to update to the latest version of Main, although for test builds this is completely unnecessary.
For tests, I always try to create a custom folder inside the test build folder. So I have to do this for absolutely EVERY COMMIT to test and give you feedback.

Again, it's not difficult, but it is very annoying that each test commit needs to be configured.

If there are any PRs with many commits, it will be very disturbing. (For example, I tested and suggested ideas in PR 1356 (the "Keyboard" PR by kalaposfos13), there were 112 commits). BUT we test not one PR, but several, and each PR has several commits. Unfortunately, inside PR we cannot update to a new commit, only Main is offered.

It would be great if builds could ignore automatic updates depending on whether they are Main or PR.

@GHU7924 commented on GitHub (Jun 7, 2025): >Turning off auto-update is not preferable, as I want to keep this turned on for the main branch. >There isn't any reason that I can think of for auto-updating PRs to main. I completely agree. >Bro just turn off automatic updates ezpz I did it, but it's a half-measure. It's not hard, but it's such an annoying choice, either you'll be constantly bothered by the update window for test PRs, or manually search for updates for the main branch, where I prefer to have automatic updates to the latest version of the emulator. >U can have user folder under ur pr testing folder and set auto update to off in that one so ur main will pick up ur global settings That's the problem. You, as a person who is directly involved in development, may not notice this, but we, as regular users from the outside, are forced to finish something to help with testing. 1) We have to re-upload every new commit if there were edits that need to be double-checked to make sure the PR is moving in the right direction and there are no regressions. 2) These commits take their settings from the global settings, i.e. config.toml, so if you have auto-update enabled, then every time you run a new test build you are ALWAYS prompted to update to the latest version of Main, although for test builds this is completely unnecessary. 3) For tests, I always try to create a custom folder inside the test build folder. So I have to do this for absolutely EVERY COMMIT to test and give you feedback. Again, it's not difficult, but it is very annoying that each test commit needs to be configured. If there are any PRs with many commits, it will be very disturbing. (For example, I tested and suggested ideas in PR 1356 (the "Keyboard" PR by kalaposfos13), there were 112 commits). BUT we test not one PR, but several, and each PR has several commits. Unfortunately, inside PR we cannot update to a new commit, only Main is offered. It would be great if builds could ignore automatic updates depending on whether they are Main or PR.

kerem referenced this issue

2026-02-27 21:14:12 +03:00

[PR #961] [MERGED] Set High Priority for Windows #1852