We use this library at GitHub to detect blob languages, highlight code, ignore binary files, suppress generated files in diffs and generate language breakdown graphs.
Linguist defines the list of all languages known to GitHub in a yaml file. In order for a file to be highlighted, a language and lexer must be defined there.
Most languages are detected by their file extension. This is the fastest and most common situation. For script files, which are usually extensionless, we do "deep content inspection"™ and check the shebang of the file. Checking the file's contents may also be used for disambiguating languages. C, C++ and Obj-C all use .h files. Looking for common keywords, we are usually able to guess the correct language.
In the actual GitHub app we deal with Grit::Blob objects. For testing, there is a simple FileBlob API.
Linguist::FileBlob.new("lib/linguist.rb").language.name #=> "Ruby"
Linguist::FileBlob.new("bin/linguist").language.name #=> "Ruby"
See lib/linguist/language.rb and lib/linguist/languages.yml.
The actual syntax highlighting is handled by our Pygments wrapper, Albino. Linguist provides a Lexer abstraction that determines which highlighter should be used on a file.
We typically run on a prerelease version of Pygments to get early access to new lexers. The lexers.yml file is a dump of the lexers we have available on our server. If there is a new lexer in pygments-main not on the list, open an issue and we'll try to upgrade it soon.
Most of the MIME types handling is done by the Ruby mime-types gem. But we have our own list of additions and overrides. To add or modify this list, see lib/linguist/mimes.yml.
MIME types are used to set the Content-Type of raw binary blobs which are served from a special raw.github.com domain. However, all text blobs are served as text/plain regardless of their type to ensure they open in the browser rather than downloading.
The MIME type also determines whether a blob is binary or plain text. So if you're seeing a blob that says "View Raw" and it is actually plain text, the mime type and encoding probably needs to be explicitly stated.
Linguist::FileBlob.new("linguist.zip").binary? #=> true
The Language Graph is built by aggregating the languages of all repo's blobs. The top language in the graph determines the project's primary language. Collectively, these stats make up the Top Languages page.
The repository stats API can be used on a directory:
project = Linguist::Repository.from_directory(".")
project.language.name #=> "Ruby"
project.languages #=> { "Ruby" => 0.98,
"Shell" => 0.02 }
These stats are also printed out by the binary. Try running linguist on itself:
$ bundle exec linguist lib/
100% Ruby
Checking other code into your git repo is a common practice. But this often inflates your project's language stats and may even cause your project to be labeled as another language. We are able to identify some of these files and directories and exclude them.
Linguist::FileBlob.new("vendor/plugins/foo.rb").vendored? # => true
See Linguist::BlobHelper#vendored? and lib/linguist/vendor.yml.
Not all plain text files are true source files. Generated files like minified js and compiled CoffeeScript can be detected and excluded from language stats. As an extra bonus, these files are suppressed in Diffs.
Linguist::FileBlob.new("underscore.min.js").generated? # => true
See Linguist::BlobHelper#generated?.
To get it, clone the repo and run Bundler to install its dependencies.
git clone https://github.com/github/linguist.git
cd linguist/
bundle install
To run the tests:
bundle exec rake test
Since this code is specific to GitHub, is not published as a official rubygem.
If you are seeing errors like StandardError: could not find any magic files!, it means the CharlockHolmes gem didn’t install correctly. See the installing section of the CharlockHolmes README for more information.
- Fork it.
- Create a branch (
git checkout -b detect-foo-language) - Make your changes
- Run the tests (
bundle installthenbundle exec rake) - Commit your changes (
git commit -am "Added detection for the new Foo language") - Push to the branch (
git push origin detect-foo-language) - Create a Pull Request from your branch.
- Promote it. Get others to drop in and +1 it.