How to INCLUDE lib files inside folder in a Git repository

I have a Git repository that contains a Libs directory in the root. This directory contains all the compiled .lib files that I want to include in the repository and push to main repo. The structure of Libs directory is:

…–| x64
……..–| Release
……..–| Debug

  • View git diff from individual parents
  • Error when generating an SSH key with Git: “no such file”
  • Git: Show content of file as it will look like after committing
  • Git Cloning a Sub-Directory in a Repository
  • using git to clone a CodePlex project that uses SVN
  • Trouble with Jenkins and Git
  • The problem is that I am unable to make Git include LIB files inside Release and Debug folders. I think its because Release and Debug folders are excluded by gitignore:

    # Build results

    What I tried:


  • Git rebase branch with merged children
  • Can Gitosis enforce correct user name/email?
  • git svn clone fails on Mac OS X: “Temp file with moniker 'svn_delta' already in use”
  • Block and/or Identify Fake author name/email in GIT
  • Can Git Remotes be Cascaded?
  • When cloning a branch : Remote branch not found in upstream origin
  • One Solution collect form web for “How to INCLUDE lib files inside folder in a Git repository”

    You would need to use:

    git add --force Libs

    In order to add them in spite of the .gitignore.

    You can check at any time which .gitignore and which rules of the .gitignore is preventing you to consider a particular folder with:

    git check-ignore -v /path/to/an/element

    For modifying your .gitignore to not ignore a particular sub-folder, consider “.gitignore exclude folder but include specific sub-folder”, especially:

    If you exclude folder/, then everything under it will always be excluded (even if some later negative exclusion pattern (“unignore”) might match something under folder/). (*)
    (*: unless certain conditions are met in git 2.?, see below)

    For instance, in your case try (git 1.8.2+):


    Note that with git 2.9.x/2.10 (mid 2016?), it might be possible to re-include a file if a parent directory of that file is excluded if there is no wildcard in the path re-included.

    Nguyễn Thái Ngọc Duy (pclouds) is trying to add this feature:

    • commit 506d8f1 for git v2.7.0, reverted in commit 76b620d git v2.8.0-rc0
    • commit 5e57f9c git v2.8.0-rc0,… reverted(!) in commit 5cee3493 git 2.8.0-rc4.

    That means, with git 2.9+, this could have worked:

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