- 09 Jan, 2022 1 commit
-
-
punkymaniac committed
-
- 13 Jul, 2018 1 commit
-
-
In attempt to provide adequate Git command analogy in regards to ignored files handling, `git_ignore_path_is_ignored` description mentions doing `git add .` on directory containing the file, and whether the file in question would be added or not - but behavior of the two matches for untracked files only, making the comparison misleading in general sense. For tracked files, Git doesn't subject them to ignore rules, so even if a rule applies, `git add .` would actually add the tracked file changes to index, while `git_ignore_path_is_ignored` would still consider the file being ignored (as it doesn't check the index, as documented). Let's provide `git check-ignore --no-index` as analogous Git command example instead, being more aligned with what `git_ignore_path_is_ignored` is about, no matter if the file in question is already tracked or not. See issue #4720 (git_ignore_path_is_ignored documentation misleading?, 2018-07-10)[1] for additional information. [1] https://github.com/libgit2/libgit2/issues/4720
Igor Djordjevic committed
-
- 08 Jan, 2013 1 commit
-
-
Edward Thomson committed
-
- 06 Jan, 2013 1 commit
-
-
Kevin Sawicki committed
-
- 20 Nov, 2012 1 commit
-
-
This adds "." ".." and ".git" to the internal ignores list by default - asking about paths with these files will always say that they are ignored.
Russell Belfer committed
-
- 24 Oct, 2012 1 commit
-
-
Ignacio Casal Quinteiro committed
-
- 15 Oct, 2012 1 commit
-
-
To answer if a single given file should be ignored, the path to that file has to be processed progressively checking that there are no intermediate ignored directories in getting to the file in question. This enables that, fixing the broken old behavior, and adds tests to exercise various ignore situations.
Russell Belfer committed
-
- 22 Aug, 2012 1 commit
-
-
This fills out the ignore API and adds tests.
Russell Belfer committed
-