mirror of
https://github.com/games-on-whales/unraid-plugin.git
synced 2026-10-15 13:02:00 +00:00
Labels
No labels
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/unraid-plugin#82
Loading…
Add table
Add a link
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?
📋 Pull Request Information
Original PR: https://github.com/games-on-whales/unraid-plugin/pull/75
Author: @JBailes
Created: 8/19/2026
Status: ✅ Merged
Merged: 8/19/2026
Merged by: @JBailes
Base:
main← Head:fix-udev-rules-update-images📝 Commits (1)
b09ced4Refresh Wolf's udev rules from Update Images too (refs #57)📊 Changes
4 files changed (+149 additions, -123 deletions)
View changed files
📝
gow.plg(+3 -0)📝
scripts/deploy.sh(+1 -123)➕
scripts/udev-rules.sh(+138 -0)📝
scripts/update.sh(+7 -0)📄 Description
install_udev_rules ran only from deploy.sh, so clicking "Update Images" pulled a new Wolf image while leaving the udev rules exactly as the last Install fetched them. The rules track Wolf's virtual device names, so a newer Wolf against older rules is precisely the gamepad-leak condition #57 describes: "after re-pulling the images today the issue seems to have resurfaced."
Same Install-vs-Update asymmetry that hid the app-state migration in #66 and the compose settings in the previous commit.
Move the rules into scripts/udev-rules.sh, following the app-state.sh precedent for code both entry points need, and call install_udev_rules from update.sh after the stack is down. The module body is unchanged from what deploy.sh had; it only gains a GO_SCRIPT default so callers that do not set it get the right path.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.