chore(github-growth): stop writing to commitfilechange language column #56491
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The original premise for writing to the
CommitFileChange
table to store thelanguage
associated with a change made in a commit was so that we could see the languages being used by organizations.We could instead save the languages associated with commits in the
Repository
table, so we wouldn't need to write toCommitFileChange
rows -- we also aren't interested in the number of changes that are being made in a particular language, just that folks are working in some language. The CommitFileChange table is also massive (1 billion plus rows) and querying is very slow.This PR removes writes to the language column in the CommitFileChange model in preparation for removing the column. Undoes #55880