Repository navigation
chore: standardize repository configuration - #3
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.
Apply the approved shared
.gitignorebaseline and retain approved repository-specific rules.Add EditorConfig defaults for LF endings and final newlines, preserve existing project settings, and require spaces for YAML. Enforce LF text attributes while preserving binary handling, saved-reference protections, and existing archive exclusions.
Codex verified ignore behavior, effective EditorConfig settings, text and binary attributes, unchanged archive exclusions for every tracked path, and
git diff --check.Investigated and written by Codex on behalf of William Jacoby (bonelifer).