chore(db): uniform exec bits on the three 644 migration scripts - #411
Merged
Conversation
git records only the owner-exec bit (755/644); group/other reconstruct from each clone's umask, so this is the only durably enforceable uniformity. All three are migrate.sh-path scripts (invoked via bash — the bit is cosmetic there); the two compose-mounted initdb scripts (01/06) were already 755, so the postgres entrypoint's execute-vs-source behavior is unchanged everywhere.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
🔧 What
Dean's uniformity intent (2026-08-07), made durable in the repo:
db/11-persona-card-migration.sh,db/18-booth-log-artist-migration.sh,db/19-persona-taste-thumb-migration.shgo100644→100755, matching the other 29.📎 Notes
migrate.sh-path scripts (invoked viabash, bit irrelevant). The two compose-mounted initdb scripts (01/06) were already 755, so the postgres entrypoint's execute-vs-source distinction changes nowhere.