Normalize line endings to LF (plus a few other tooling things) #133
Conversation
This file contains 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
throwaway96
changed the title
throwaway96
force-pushed
the
eol-normalize-20240324
branch
3 times, most recently
from
95c6cb1 to
5ae5b57
Compare
Add .gitattributes files to ensure git knows which files are text. Ensure that shell scripts (including .husky/pre-commit) use LF.
Ignore .vscode directory and make some other entries more specific.
Remove execute permission from several data files.
Specify the Chromium version used for WAM on each webOS major version.
throwaway96
force-pushed
the
eol-normalize-20240324
branch
from
5ae5b57 to
1beb520
Compare
mariotaku
approved these changes
Mar 25, 2024
throwaway96
added a commit
to throwaway96/youtube-webos
that referenced
this pull request
Mar 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This should behave like
autocrlf, except for the.husky/pre-commitshell script, which is forced to use LF line endings. (This will also apply to any future shell scripts with a.shextension.)Otherwise, this PR doesn't force text files in the working tree to use LF, although I'd like to hear opinions on whether or not that would be desirable. Even on Windows, most editors can handle LF these days.
Bonus changes: ignore the
.vscodedirectory, addlint/prettier-checkscripts topackage.json, and fix file modes.