Ingore changes to .direnv and .gitignore #475
Closed
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
The Direnv[0] tool is useful to run within rules (by prefixing commands with "direnv exec .") but it creates a cache of metadata at .direnv which Tup should not be tracking. It may also make changes to .gitignore which would not effect reasonable build jobs. 0: https://direnv.net/
|
s/Ingore/Ignore/g This should be two separate commits. Not sure why you would want to ignore the Gitignore tho. |
ghost
closed this by deleting the head repository
This pull request was closed.
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.
The Direnv tool is useful to run within rules (by prefixing commands with "direnv exec .") but it creates a cache of metadata at .direnv which Tup should not be tracking. It may also make changes to .gitignore which would not effect reasonable build jobs.
This is a quick and simple fix, an alternative would be to add some sort of general "tupignore" mechanism for ignoring the cache artifacts created by various tools.