repo: stop tracking the local opam switch and dune-workspace - #294
Merged
Conversation
The _opam symlink points at one machine's absolute path, and both files are local build setup that a checkout supplies for itself.
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.
Two local build-setup files reached main by accident in #285: _opam is a symlink to one machine's absolute path, so a fresh clone gets a dangling link named _opam that shadows the _opam/ ignore rule, and dune-workspace is per-checkout configuration. Both are untracked again and dune-workspace joins .gitignore beside _opam/. My mistake - a git add -A while rewording that PR swept them in.