Repository navigation
chore(linux): own ignore, editorconfig and generated-file attributes - #3535
Merged
Merged
Conversation
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
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.
Why
Linux build dirs were ignored partly by the root file and partly not at all, editors used the root's 4-space indent on Meson, GtkBuilder and CSS files, and the banned-words check exempted license text by a hard-coded Linux path list.
Change
linux/.gitignoreowns_build/, adds_flatpak/and.flatpak-builder/, and drops lines the root covers plusdocs/audit-*.md, a local file nothing references.linux/.editorconfigoverrides the root with the indentation the files already use..gitattributesmarks the Linux generated fileslinguist-generated, and verbatim license texts and the SQLite headerslinguist-vendored.check-banned-words.shskips a diff file with either attribute set.Verified
The new
test_check_banned_words.pyfails on the old script. Old and new flag the same lines over seven bases and a staged change, minus the newly vendored files; shellcheck 0.9.0 is clean.