Feature: get use of GitHub's all supported languages list (linguist)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 723
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
GitHub uses linguist to detect blob languages, ignore binary or vendored files, suppress generated files in diffs, and generate language breakdown graphs.
Languages-related interfaces were added in PR #1979, #1992, and #2001. However, now all the const LanguageNames in clients.languages.go are still manually added and are a subset of linguist's languages.yaml containing popular languages (not all) supported by GitHub.
Describe the solution you'd like
Should we use all the langauge names in this language list (linguist's languages.yaml) in scorecard? How?
FYI, I think other fields in linguist's languages.yaml such as extensions might be useful when scanning repo files for a specific language.
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read clients/languages.go and compare its LanguageNames constants with GitHub Linguist's languages.yml. Trace the language-related interfaces added in PRs #1979, #1992, and #2001, and determine the intended scope for names and extensions. The work is done when a specific integration approach and acceptance criteria for supported languages are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go, yaml
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100