Add option to gitadd to allow for git resolvable pathspecs #108
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
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.
I need the ability to pass fileglob pathspecs (http://git-scm.com/docs/git-add - see the options / pathspec section) directly to the git add command without grunt attempting to resolve it to an actual explicit list of files via grunt.task.files.src.
This is particularly needed/useful for platforms (i.e. windows) that are constrained by a max command line limit of 8k characters. Providing the ability to specify pathspecs directly to the git add command is extremely valuable/useful to fix scenarios in which many files are attempting to be added in a single git add command or even when a few of the files attempting to be added have a long path.