bitHound Blog

Ignoring files and folders in bitHound

As you will see in the example below, sometimes there are cases when it is best for bitHound to ignore particular files such as vendor or minified files. While we handle the common cases, your project may have some unique files such as a built, minified file, or a dist folder you don't want bitHound to analyze. It's because of this that we've introduced a .bithoundrc configuration file that allows you to specify files and folders you want bitHound to ignore.

How to use it

Using .bithoundrc is easy. It's a JSON formatted file that you commit to your project's root folder. See this gist of our default list of ignored file and use it as an example of proper formatting.

The next time bitHound analyzes your project and picks up the new commit, we'll ignore the files and folders you listed. Those files and folders will be ignored from that commit onward.

Please note

Adding your own .bithoundrc to your repository will replace our standard set of ignored files and folders. Our gist shows our default list. If you want bitHound to continue any of these files and folders, be sure to keep it in the .bithoundrc file you add.

bitHound identifies risks and priorities in your Node.js projects.