docs(TODO): record #120 - respect .gitkeep in gitignore handling [DISCUSS] - #287
Merged
Conversation
…CUSS] Open question captured: respect .gitkeep always when .gitignore is active, or only in an advanced gitignore mode? .gitkeep is a pure convention, so the concrete semantics (don't prune/hide a dir whose only content is .gitkeep, etc.) need pinning first; leaning always-on since it's a ubiquitous convention. Note xff already honors an explicit !.gitkeep negation.
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.
Captures a new backlog item (#120): respect
.gitkeepfiles when xff handles.gitignore(extends the ignore family #80/#95).Open question recorded: respect
.gitkeepalways whenever.gitignoreis active, or only in an advanced gitignore mode?.gitkeepis a pure convention (git itself has no notion of it) for keeping an otherwise-empty directory, so the concrete semantics need pinning first (e.g. don't prune/hide a directory whose only content is a.gitkeep; treat it as a keep signal). Note xff already honors an explicit!.gitkeepnegation - this is about implicit handling.Leaning always-on (ubiquitous convention, no downside), but the semantics get decided before building. Docs-only.