Add LFS locking checks for .uasset and .umap files in repository status #192
Conversation
This file contains 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
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.
This check provides a helpful warning if git LFS lockable attributes are not detected by the plugin.
The plugin only checks at the root of the git repo to decide if the repo can support LFS lock.
The check will fail when there is an issue with .gitattributes: if your project in not at the root of the repo or you're using the old content/** configuration from the default plugin.
If the check fails, it will disable git LFS locking, otherwise the plugin has a behavior, believing he can lock files but can't.