From: Shourya Shukla <shouryashukla.oo@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, sandals@crustytoothpaste.net,
Shourya Shukla <shouryashukla.oo@gmail.com>
Subject: [PATCH v3 1/4] gitfaq: files in .gitignore are tracked
Date: Tue, 21 Apr 2020 18:42:20 +0530 [thread overview]
Message-ID: <20200421131223.29337-2-shouryashukla.oo@gmail.com> (raw)
In-Reply-To: <20200421131223.29337-1-shouryashukla.oo@gmail.com>
Add issue in 'Common Issues' section which addresses the problem of
Git tracking files/paths mentioned in '.gitignore'.
Signed-off-by: Shourya Shukla <shouryashukla.oo@gmail.com>
---
Documentation/gitfaq.txt | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/Documentation/gitfaq.txt b/Documentation/gitfaq.txt
index 1cf83df118..96767e7c75 100644
--- a/Documentation/gitfaq.txt
+++ b/Documentation/gitfaq.txt
@@ -223,6 +223,27 @@ a file checked into the repository which is a template or set of defaults which
can then be copied alongside and modified as appropriate. This second, modified
file is usually ignored to prevent accidentally committing it.
+[[files-in-.gitignore-are-tracked]]
+I asked Git to ignore various files, yet they are still tracked::
+ Git ignores files matching the patterns stated in the '.gitignore'.
+ Consequently, `git add` does not add the files/paths matching the
+ pattern in `.gitignore`, meaning they remain untracked; `git status`
+ does not list the aforementioned files/paths as untracked.
+
+ One thing to note is that the `.gitignore` mechanism applies only
+ to the files that are not already tracked. A file/path that is
+ already tracked will stay to be tracked even if you add a pattern
+ that happens to match it to `.gitignore` file.
+
+ This is probably the reason why Git shows some files/paths in the
+ staging area. These entities were being tracked before and later
+ were added in the `.gitignore`, due to which they show up in the
+ staging area.
+
+ To completely ignore and untrack files/paths falling in the above
+ category, it is advised to use `git rm --cached <file>` as well as
+ add these files/paths in the `.gitignore`.
+
Hooks
-----
--
2.20.1
next prev parent reply other threads:[~2020-04-21 13:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 13:12 [PATCH v3 0/4] gitfaq: add issues in the 'Common Issues' section Shourya Shukla
2020-04-21 13:12 ` Shourya Shukla [this message]
2020-04-21 19:45 ` [PATCH v3 1/4] gitfaq: files in .gitignore are tracked Junio C Hamano
2020-04-21 13:12 ` [PATCH v3 2/4] gitfaq: changing the remote of a repository Shourya Shukla
2020-04-21 19:54 ` Junio C Hamano
2020-04-27 17:30 ` Shourya Shukla
2020-04-21 13:12 ` [PATCH v3 3/4] gitfaq: shallow cloning " Shourya Shukla
2020-04-21 20:00 ` Junio C Hamano
2020-04-21 20:43 ` Randall S. Becker
2020-04-21 20:57 ` Junio C Hamano
2020-04-21 21:25 ` Randall S. Becker
2020-04-22 1:30 ` Derrick Stolee
2020-04-22 4:00 ` Jonathan Nieder
2020-04-22 0:13 ` Elijah Newren
2020-04-21 13:12 ` [PATCH v3 4/4] gitfaq: fetching and pulling " Shourya Shukla
-- strict thread matches above, loose matches on Subject: below --
2020-04-21 13:11 [PATCH v3 0/4] gitfaq: add issues in the 'Common Issues' section Shourya Shukla
2020-04-21 13:11 ` [PATCH v3 1/4] gitfaq: files in .gitignore are tracked Shourya Shukla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200421131223.29337-2-shouryashukla.oo@gmail.com \
--to=shouryashukla.oo@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.