• File size measurements show the distribution of size of files.
• Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
• It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.

• There are 201 files with 19,545 lines of code.
• 3 very long files (5,621 lines of code)
• 0 long files (0 lines of code)
• 16 medium size files (4,443 lines of codeclsfd_ftr_w_mp_ins)
• 32 small files (4,297 lines of code)
• 150 very small files (5,184 lines of code)

There are 58 files with lines longer than 120 characters. In total, there are 401 long lines.

File	# lines	# units	# long lines
main.tf in buildkite/terraform/bazel	1707	-	157
bazelci.py in buildkite	2762	130	33
main.tf in buildkite/terraform/bazel-testing	185	-	25
bazel_auto_sheriff.py in buildkite	421	30	17
main.tf in buildkite/terraform/bazel-trusted	203	-	16
continuous-integration.yml in pipelines	66	-	12
setup-windows.ps1 in buildkite	274	-	11
GithubIssueList.tsx in dashboard/client/src	1152	26	9
flakiness.go in metrics/metrics	107	6	8
cloudsql_gc.go in metrics/publishers	115	11	7
aggregated_pipeline_performance.go in metrics/metrics	48	6	5
main.go in metrics	124	5	5
bazel-release.yml in pipelines	395	-	5
bcr_presubmit.py in buildkite/bazel-central-registry	203	19	5
zombie_instances.go in metrics/metrics	87	8	4
mac_performance.go in metrics/metrics	51	4	4
critical_path.go in metrics/metrics	60	6	4
startup-windows-pdssd.ps1 in buildkite	146	-	4
daily_performance.go in metrics/metrics	78	8	3
pipeline_performance.go in metrics/metrics	79	7	3