All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shourya Shukla <shouryashukla.oo@gmail.com>
To: kreska07@gmail.com
Cc: git@vger.kernel.org
Subject: Re: file is showing as modified even that it was never commited
Date: Mon, 4 May 2020 11:25:30 +0530	[thread overview]
Message-ID: <20200504055530.GA13290@konoha> (raw)
In-Reply-To: <CAEoQP9iY-0+=ETA0vrHL0HngccwtNA_3KX4WSSokJpOgJDGUeA@mail.gmail.com>

Hey Ewa!

This might be the fix for you:

A `gitignore` file ensures that certain file(s) which are not
tracked by Git remain untracked.  However, sometimes particular
file(s) may have been tracked before adding them into the
`.gitignore`, hence they still remain tracked.  To untrack and
ignore files/patterns, use `git rm --cached <file/pattern>`
and add a pattern to `.gitignore` that matches the <file>.

Most probably the '.idea' folder might have been tracked before adding
it to the '.gitignore' and hence it shows up in the staging area (i.e.,
when you run a `git status`, it shows up as modified).

If there is a doubt still, feel free to drop a message here :)

Regards,
Shourya Shukla


  reply	other threads:[~2020-05-04  5:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEoQP9gVur=UDDPzHnLq-AryDnd45uYdEs3kajzLrtr572e_rA@mail.gmail.com>
2020-05-03 20:03 ` file is showing as modified even that it was never commited Ewa Śliwińska
2020-05-04  5:55   ` Shourya Shukla [this message]
2020-05-04  8:17     ` Ewa Śliwińska
     [not found]     ` <CAEoQP9hyMi=oj18atTJo+dR3ve_zzrLQoOja0CKAAVHei6rA0g@mail.gmail.com>
2020-05-04 12:00       ` Shourya Shukla
2020-05-04 12:11         ` Ewa Śliwińska
2020-05-04 17:17           ` Sergey Organov
2020-05-04 18:39             ` Ewa Śliwińska
2020-05-04 19:51               ` Sergey Organov
2020-05-04 20:04                 ` Ewa Śliwińska
2020-05-04 20:41               ` Andreas Schwab
2020-05-05  7:49                 ` Ewa Śliwińska
2020-05-05  8:07                   ` Andreas Schwab
2020-05-05  8:10                     ` Ewa Śliwińska
2020-05-05  8:14                       ` Andreas Schwab
2020-05-05  8:19                         ` Ewa Śliwińska
2020-05-05  8:25                           ` Andreas Schwab
2020-05-05  8:34                             ` Ewa Śliwińska

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=20200504055530.GA13290@konoha \
    --to=shouryashukla.oo@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=kreska07@gmail.com \
    /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.