Fix executable bit on Solo theme image assets#553
Conversation
default-skin.png, default-skin.svg, and preloader.gif in packages/solo are committed with mode 100755 (executable). They are static binary image assets and should not be executable. On self-hosted Ghost installs this trips the `ghost doctor` / `ghost update` file-permission check, which expects 644/664. This sets their mode to 100644; content is unchanged (blob SHAs are identical). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (3)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
packages/solo/assets/images/default-skin.png,default-skin.svg, andpreloader.gifare committed with mode100755(executable bit set). These are static binary image assets and shouldn't be executable.This is a permission-only change — the file content is untouched (blob SHAs are identical), only the mode changes from
100755→100644.Why this matters
On self-hosted Ghost installs, the executable bit causes the
ghost doctor/ghost updatefile-permission check to flag these files (it expects644/664):Resetting the mode to
100644clears the warning, matching every other asset in the theme.Notes
packages/solois affected; I didn't touch other themes, though it may be worth checking whether the same exec-bit slipped into other packages.