chore(git): sync .gitignore to match v2-displays (drop trailing newline)#334
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
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.
Cherry-picks the
.gitignorechange fromv2-displays(commit 7df26a0) ontomainso the two branches'.gitignorefiles are byte-identical.Why
The
Validate FilenamesCI job diffs every PR against hardcodedorigin/main. Becausev2-displays's.gitignorediffers frommain's by a single trailing newline, every PR based onv2-displays(e.g. the merged display PRs #325/#326, and the new telemetry PR #332) has.gitignorespuriously flagged as "should not exist" and the job goes red.Bringing
main's.gitignorein line withv2-displaysremoves that false positive at the source, without touching the CI workflow.Diff is a single line — the only difference was the trailing newline.
🤖 Generated with Claude Code