Git ignore deleted files

I have a website project that has more than 50,000 unimportant files (to development) in some directories.

/website.com/files/1.txt
/website.com/files/2.txt
/website.com/files/3.txt
/website.com/files/etc.txt

The stuff in /files is already in the repo. I want to delete all the files in /files on my local copy but I want git to ignore it so it doesn’t delete them when I do a pull on the web server.

  • Unstage all deleted files in Git
  • Windows batch file to delete .svn files and folders
  • How do I .gitignore and delete an already committed file without affecting other working copies?
  • Undo delete in GIT
  • Ignore deleted files in git?
  • How do I completely nuke a file from a git repo?
  • Any ideas?

  • Ensuring relative Git paths
  • Is there a good way to rebase and merge the project.pbxproj file using git?
  • Difference between nested git repos and submodules
  • How to execute a command right after a fetch or pull command in git?
  • Move .git repo to parent directory
  • How to resolve ALL conflicts using HEAD, with any mergetool
  • 4 Solutions collect form web for “Git ignore deleted files”

    Ignoring a whole directory didn’t work. I had to do this:

    for i in `git status | grep deleted | awk '{print $3}'`; do git update-index --assume-unchanged $i; done
    

    The code below works on deleted as well as modified files to ignore it when you do a git status.

     git update-index --assume-unchanged dir-im-removing/
    

    or a specific file

    git update-index --assume-unchanged config/database.yml
    

    Ignore modified (but not committed) files in git?

    Beware: The suggestion above for deleted files when you do a “git commit -am ” includes the deleted file!

    A solution that would work for me is to instead of deleting the file, just make it’s content blank. This is what I used to mute a .htaccess file.

    Creating a sub-repo is one solution, but you should make that sub-repo a submodule.

    That way:

    • you keep a link between your normal content and that ‘files’ content
    • if the ‘files’ content evolves one day, you can register its evolution in the main repo
    • you can checkout your main repo without ” git submodule update ” (that is without filling the ‘files‘ content
    • on deployment, a git submodule update after the git submodule init will be enough to get back the right version of the ‘files‘ content.

    Ok Ive found a solution. Simply create a new repo in the sub directories and the parent repo will ignore them.

    Git Baby is a git and github fan, let's start git clone.