Idea: back up the saves before a pull request's build first starts (or give those builds saves of their own) #375
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/upscaling
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
testing wanted
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot#375
Loading…
Reference in a new issue
No description provided.
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?
The idea
Before a pull request's build starts for the first time, the launcher backs up the saves every version shares (as Manage saves > Export does), and offers them back after. Better still, as the mock in #337 showed, a pull request's build gets saves of its own.
Why: these builds run code nobody has reviewed, against the player's real saves. The picker asks people to export first, which is easy to skip.
Anything else
A follow-up of #337 (testing pull requests from the launcher): CI in #353, the launcher's picker in LongshotLauncher pull request 59.
gab9281 referenced this issue2026-11-14 06:49:51 +00:00
Opened by mistake: its idea is now a follow-up in the list on #337. Closing; a maintainer may delete it.