git check-ignore Use git check-ignore command to debug your gitignore file (exclude files). For example: $ git check-ignore -v config.php .gitignore:2:src config.php The above output details about the matching pattern (if any) for each given pathname (including line). So maybe your file extension is not ignored, but the whole directory. The returned format is: <source> … Read more
In contrast to what the name “ignore” might suggest. .gitignore is only consulted when you git add files: in other words a file already added to the (index of the) repository will not be excluded based on the .gitignore. First you better modify the .gitignore such that the file is no longer added. Add the … Read more
Just wanted to summarize for possible quick future reference — the leading slash anchors the match to the root. Thus, in the example below, without the slash, the wildcard would also exclude everything within foo because it would take * and move recursively down the tree. However, with /*, it excludes everything except folder foo … Read more
You can try a combination similar to: * !/**/ !*.* That gitignore exclusion rule (a negated pattern) should ignore all files, except the ones with an extension. As mentioned below by Mad Physicist, the rule is: It is not possible to re-include a file if a parent directory of that file is excluded. (*) (*: … Read more
The only directory you want excluded from version control is .meteor/local. Meteor automatically creates the right .meteor and .meteor/.gitignore, though — you shouldn’t need to do anything.
Yes, you can. Try it, it works fine. Put a .gitignore in the root of your repo, and put another .gitignore with additional things to ignore in a subdirectory.
The official Bower page stated: N.B. If you aren’t authoring a package that is intended to be consumed by others (e.g., you’re building a web app), you should always check installed packages into source control. Make sure to check out the link in the quote, it discusses some pro and cons. The main pro it … Read more
You can create your own .gitignore using git config –global core.excludesfile $HOME/.gitignore Then put your desired entries in that file.
As already been said, to exclude from status just use: git status -uno # must be “-uno” , not “-u no” If you instead want to permanently ignore currently untracked files you can, from the root of your project, launch: git status –porcelain | grep ‘^??’ | cut -c4- >> .gitignore Every subsequent call to … Read more
I’m not sure why this doesn’t work for you. In case it helps, here’s a typical .gitignore file from one of my Visual Studio/git projects: *.suo *.user _ReSharper.* bin obj packages