1

as above.

here's the content of .gitignore (located in project main folder)

➜  pwd
/Volumes/drive2/my-project

➜  cat .gitignore
.project

/config/file-im-trying-to-ignore.txt
config/file-im-trying-to-ignore.txt
file-im-trying-to-ignore.txt

These are the steps I used when making the changes:

  • edit .gitignore
  • commit
  • edit file-im-trying-to-ignore.txt

What am i doing wrong?

I've commited my repo after making changes to .gitignore and then made changes to file-im-trying-to-ignore.txt

I used these 2 sites as reference:

Thank you

mrjayviper
  • 2,165
  • 10
  • 38
  • 77
  • 1
    May be a long shot, but try investigating encoding of a file - I had trouble for long time with this - it simply did not work as it should. It turned out I had some wild encoding (othher than any UTF or Unicode), which was not correctly understood by git. Make sure it is set to UTF-8 – Michał Turczyn Jan 11 '21 at 06:43
  • 2
    Does [this answer](/a/36713835/4265352) help? – axiac Jan 11 '21 at 06:45
  • @axiac that fixed it for me. Can you please leave that as an answer so I can accept it? Thank you. – mrjayviper Jan 11 '21 at 06:49

3 Answers3

1

Is your file already indexed? .gitignore affects only files that are not indexed by Git (staged or committed).

If your file just staged and never committed before - you should unstage file with git reset HEAD your_file. Docs.

Or, if your file was committed previously, thus indexed in Git, you should remove it from index with git rm --cached your_file, then commit. Then .gitignore takes effect. Docs. Clean the file from .gitignore while removing it from cache, then add it back there.

Som-1
  • 386
  • 2
  • 10
  • Git reset might be used in both cases with appropriate flag (`--soft` `--medium` or `--hard`) – Michał Turczyn Jan 11 '21 at 06:52
  • Well, probably. Have not used it this way, but as I remember, it will reset the whole commit, and from the latest back, not the single file. Flags just specify what changes to keep or delete in the working tree. – Som-1 Jan 11 '21 at 07:05
  • Yes, you are correct :) Forgot about that. – Michał Turczyn Jan 11 '21 at 08:09
1

If the file is already committed and pushed to your repository, you must untrack the file where you will add to .gitignore, then .gitignore only works on untracked files. To untrack files, run following command:

// untrack all files
$ git rm -r --cache

// untrack one specific file
$ git rm --cache filename.txt

After untracking the file, you can add (git add .), commit (git commit -m ".gitignore now ignores the file") and push (git push) it to your repository.

SwissCodeMen
  • 3,359
  • 4
  • 15
  • 26
-1

Have you tried using git reset to untrack the file? https://git-scm.com/docs/git-reset

Roland Warburton
  • 73
  • 7