Skip to main content
Relevant Files

How does Velocity determine which files are relevant?

J
Written by James McGill
Updated over 5 months ago

Relevant Files

To provide a more accurate view of coding activity within your organization, Velocity automatically excludes the contents of vendored dependencies and auto-generated files for common languages and frameworks. As a result, Velocity often reports a smaller, but more accurate, number of lines modified in a Pull Request or Commit compared to GitHub, GitLab, or Bitbucket.
​
You can use File Rules to override Velocity's default exclusions or to add additional exclusions.

Why

This approach gives a significantly more accurate view into the work being done within your Engineering team.
​
Consider a commit which:

  • Adds a new class (100 Lines of Code)

  • Adds a test for this class (25 Lines of Code)

  • Copies a third-party library into a third_party directory so that it can be used by the new class (4,096 Lines of Code)

Most systems would report this as a net addition of 4,221 Lines of Code - however the large majority of this was not authored by your team.
​
Velocity will - correctly - report this change as 125 Lines of Code.

Did this answer your question?