bitHound Blog

Branch analysis results on your Pull Requests

Bring the power of bitHound directly to your workflow by enabling branch status checks on your Pull Requests on GitHub and Bitbucket – for both public and private projects.

GitHub Pull Requests with bitHound branch status

We've added options for several criteria so you can add fine-grain control on your pull requests for both dependencies and code issues. For dependencies check for insecure dependencies, outdated dependencies over 3 months and more. We have you covered on the code side with looking for duplicate functions, complex functions, ignored errors and more. Choose which criteria you want to enable to fit the needs of your project!

Just like enabling our automatic commit analysis integration, this too will require admin-level access to that project on GitHub or Bitbucket. To get started, go to your project Settings > Integrations and enable Automatic Commit Analysis using Webhooks (if its not already on) and then enable Failing Criteria to display the option to enable Branch Status on Pull Requests. You can also specify your conditions for failing a pull request in the Failing Criteria section above.

Set up PR Status

We should note however that this will only apply to future Pull Requests issued after you've completed the above setup.

That's it! Get started today and bring bitHound right into your pull requests!

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