git-check-ignore - Debug gitignore / exclude files


   git check-ignore [options] pathname...
   git check-ignore [options] --stdin


   For each pathname given via the command-line or from a file via
   --stdin, check whether the file is excluded by .gitignore (or other
   input files to the exclude mechanism) and output the path if it is

   By default, tracked files are not shown at all since they are not
   subject to exclude rules; but see '--no-index'.


   -q, --quiet
       Don't output anything, just set exit status. This is only valid
       with a single pathname.

   -v, --verbose
       Also output details about the matching pattern (if any) for each
       given pathname. For precedence rules within and between exclude
       sources, see gitignore(5).

       Read pathnames from the standard input, one per line, instead of
       from the command-line.

       The output format is modified to be machine-parseable (see below).
       If --stdin is also given, input paths are separated with a NUL
       character instead of a linefeed character.

   -n, --non-matching
       Show given paths which don't match any pattern. This only makes
       sense when --verbose is enabled, otherwise it would not be possible
       to distinguish between paths which match a pattern and those which

       Don't look in the index when undertaking the checks. This can be
       used to debug why a path became tracked by e.g.  git add .  and was
       not ignored by the rules as expected by the user or when developing
       patterns including negation to match a path previously added with
       git add -f.


   By default, any of the given pathnames which match an ignore pattern
   will be output, one per line. If no pattern matches a given path,
   nothing will be output for that path; this means that path will not be

   If --verbose is specified, the output is a series of lines of the form:

   <source> <COLON> <linenum> <COLON> <pattern> <HT> <pathname>

   <pathname> is the path of a file being queried, <pattern> is the
   matching pattern, <source> is the pattern's source file, and <linenum>
   is the line number of the pattern within that source. If the pattern
   contained a ! prefix or / suffix, it will be preserved in the output.
   <source> will be an absolute path when referring to the file configured
   by core.excludesFile, or relative to the repository root when referring
   to .git/info/exclude or a per-directory exclude file.

   If -z is specified, the pathnames in the output are delimited by the
   null character; if --verbose is also specified then null characters are
   also used instead of colons and hard tabs:

   <source> <NULL> <linenum> <NULL> <pattern> <NULL> <pathname> <NULL>

   If -n or --non-matching are specified, non-matching pathnames will also
   be output, in which case all fields in each output record except for
   <pathname> will be empty. This can be useful when running
   non-interactively, so that files can be incrementally streamed to STDIN
   of a long-running check-ignore process, and for each of these files,
   STDOUT will indicate whether that file matched a pattern or not.
   (Without this option, it would be impossible to tell whether the
   absence of output for a given file meant that it didn't match any
   pattern, or that the output hadn't been generated yet.)

   Buffering happens as documented under the GIT_FLUSH option in git(1).
   The caller is responsible for avoiding deadlocks caused by overfilling
   an input buffer or reading from an empty output buffer.


       One or more of the provided paths is ignored.

       None of the provided paths are ignored.

       A fatal error was encountered.


   gitignore(5) git-config(1) git-ls-files(1)


   Part of the git(1) suite


Personal Opportunity - Free software gives you access to billions of dollars of software at no cost. Use this software for your business, personal use or to develop a profitable skill. Access to source code provides access to a level of capabilities/information that companies protect though copyrights. Open source is a core component of the Internet and it is available to you. Leverage the billions of dollars in resources and capabilities to build a career, establish a business or change the world. The potential is endless for those who understand the opportunity.

Business Opportunity - Goldman Sachs, IBM and countless large corporations are leveraging open source to reduce costs, develop products and increase their bottom lines. Learn what these companies know about open source and how open source can give you the advantage.

Free Software

Free Software provides computer programs and capabilities at no cost but more importantly, it provides the freedom to run, edit, contribute to, and share the software. The importance of free software is a matter of access, not price. Software at no cost is a benefit but ownership rights to the software and source code is far more significant.

Free Office Software - The Libre Office suite provides top desktop productivity tools for free. This includes, a word processor, spreadsheet, presentation engine, drawing and flowcharting, database and math applications. Libre Office is available for Linux or Windows.

Free Books

The Free Books Library is a collection of thousands of the most popular public domain books in an online readable format. The collection includes great classical literature and more recent works where the U.S. copyright has expired. These books are yours to read and use without restrictions.

Source Code - Want to change a program or know how it works? Open Source provides the source code for its programs so that anyone can use, modify or learn how to write those programs themselves. Visit the GNU source code repositories to download the source.


Study at Harvard, Stanford or MIT - Open edX provides free online courses from Harvard, MIT, Columbia, UC Berkeley and other top Universities. Hundreds of courses for almost all major subjects and course levels. Open edx also offers some paid courses and selected certifications.

Linux Manual Pages - A man or manual page is a form of software documentation found on Linux/Unix operating systems. Topics covered include computer programs (including library and system calls), formal standards and conventions, and even abstract concepts.