2

I have a Gemfile.lock that git simply will not ignore. It's in my gitignore file (see below) but it keeps showing under unstaged changes whenever I bundle install. Anyone else ever run into something like this? Thanks in advance.

My Gitignore looks like this:

/.tags*
/log
/tmp
/db/*.sqlite3
/public/system
/coverage/
/spec/tmp
**.orig
rerun.txt
Gemfile.lock
...
neanderslob
  • 2,633
  • 6
  • 40
  • 82
  • Possible duplicate of [How to make Git "forget" about a file that was tracked but is now in .gitignore?](https://stackoverflow.com/questions/1274057/how-to-make-git-forget-about-a-file-that-was-tracked-but-is-now-in-gitignore) – 1615903 Jan 25 '19 at 07:30

1 Answers1

8

Is it because the Gemfile.lock is already committed to your repository? Is it showing as a new file (with ?? in git status) or a modification (with M in git status). If it's the latter then you will need to remove the file with git rm Gemfile.lock. Once you commit that change then the file should stop showing up in git status.

As an aside, it's generally best practice to keep the Gemfile.lock committed to the repository (unless this is a gem). Here's a good SO question about that topic: Should Gemfile.lock be included in .gitignore?

tpett
  • 846
  • 6
  • 7