Make run.sh executable - #13
Open
willryker wants to merge 1 commit into
Open
Conversation
Content is unchanged; this is a mode change only, 100644 -> 100755. The README tells you to invoke it directly (`sudo ./run.sh`, and again under the manual-launch instructions), and its sibling scripts setup.sh and watchdogs-launcher are both already committed as 100755. setup.sh itself does `chmod +x run.sh` at install time, which is what makes a fresh clone work -- so the tracked mode has simply been out of step with how the file is used. Committing the bit means a clone can run ./run.sh without setup.sh having to patch it first, and stops the chmod showing up as a permanent dirty file in git status afterwards. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01DZnaedMVnFLztkCsmWGVfv
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make
run.shexecutableMode change only,
100644->100755. No content is modified — the diff is1 file changed, 0 insertions(+), 0 deletions(-).run.shis currently the only launcher script tracked as non-executable:mainrun.sh100644setup.sh100755watchdogs-launcher100755That is out of step with how the file is documented and used. The README invokes
it directly in three places (
sudo ./run.sh, and twice under the manual launchinstructions), and
setup.shprintsRun the game: sudo ./run.shoncompletion. A fresh clone cannot do that until
setup.shline 316(
[ -f "run.sh" ] && chmod +x run.sh) patches the bit at install time.Two small benefits from tracking the bit instead:
./run.shworks straight from a clone, without depending onsetup.shhavingbeen run first — useful for anyone launching the game manually or from a
desktop entry rather than through the installer.
setup.sh'schmodstops showing up as a permanent modification ingit statusafterwards, which currently leaves every installed copy with adirty working tree.
Split out of #12 deliberately, since it is unrelated to the bridge changes there.
🤖 Generated with Claude Code
https://claude.ai/code/session_01DZnaedMVnFLztkCsmWGVfv