azure / transition_embeddings_model

Intro

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.

File Size Overall

Legend:

1001+

501-1000

201-500

101-200

1-100

File Size per Extension

1001+

501-1000

201-500

101-200

1-100

File Size per Logical Decomposition

primary

1001+

501-1000

201-500

101-200

1-100

Longest Files (Top 2)

File	# lines	# units
migrate.py in root	150	9
function_app.py in custom_skillset	45	1

Files With Most Units (Top 2)

File	# lines	# units
migrate.py in root	150	9
function_app.py in custom_skillset	45	1

Files With Long Lines (Top 1)

There is only one file with lines longer than 120 characters. In total, there are 10 long lines.

File	# lines	# units	# long lines
migrate.py in root	150	9	10

Correlations

File Size vs. Commits (all time): 2 points

		150.0	lines of code min: 45.0 average: 97.5 25th percentile: 45.0 median: 97.5 75th percentile: 150.0 max: 150.0
0	1.0
commits (all time) min: 1.0 \| average: 1.0 \| 25th percentile: 1.0 \| median: 1.0 \| 75th percentile: 1.0 \| max: 1.0

		150.0	lines of code min: 45.0 average: 97.5 25th percentile: 45.0 median: 97.5 75th percentile: 150.0 max: 150.0
0	1.0
contributors (all time) min: 1.0 \| average: 1.0 \| 25th percentile: 1.0 \| median: 1.0 \| 75th percentile: 1.0 \| max: 1.0

No data for "commits (30d)" vs. "lines of code".

No data for "contributors (30d)" vs. "lines of code".

No data for "commits (90d)" vs. "lines of code".

No data for "contributors (90d)" vs. "lines of code".