Disable git's fsmonitor on repositories managed by opam - #7090
Draft
kit-ty-kate wants to merge 1 commit into
Draft
Disable git's fsmonitor on repositories managed by opam#7090kit-ty-kate wants to merge 1 commit into
kit-ty-kate wants to merge 1 commit into
Conversation
kit-ty-kate
commented
Aug 25, 2026
| let git_config = [ | ||
| "gc.autoDetach", "false"; | ||
| "maintenance.autoDetach", "false"; | ||
| "core.fsmonitor", "false"; |
Member
Author
There was a problem hiding this comment.
TODO:
- add a comment here telling people to think about adding
git config --localvariable - add the
git config --localvariable - idea from @rjbou: we could also simply map the list to create these
git config --localinstead of duplicating them.
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.
Fixes #7054
As mentioned in this ticket this is barely worth doing as one would need to set an undocumented environment variable to trigger the issue but i guess it's best to make sure it never happens and we already have the code for it anyway.