mirror of
https://github.com/KevinMidboe/linguist.git
synced 2025-10-29 17:50:22 +00:00
Rearrange docs
This commit is contained in:
Brandon Keepers
@@ -1,33 +1,68 @@
|
|||||||
## Contributing
|
# Contributing
|
||||||
|
|
||||||
The majority of contributions won't need to touch any Ruby code at all. The [master language list][languages] is just a YAML configuration file.
|
The majority of contributions won't need to touch any Ruby code at all. Linguist defines a list of all languages known to GitHub in [lib/linguist/languages.yml](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
|
||||||
|
|
||||||
Almost all bug fixes or new language additions should come with some additional code samples. Just drop them under [`samples/`][samples] in the correct subdirectory and our test suite will automatically test them. In most cases you shouldn't need to add any new assertions.
|
Most languages are detected by their file extension. For disambiguating between files with common extensions, we first apply some common-sense heuristics to pick out obvious languages. After that, we use a [statistical classifier](https://github.com/github/linguist/blob/master/lib/linguist/classifier.rb). This process can help us tell the difference between, for example, `.h` files which could be either C, C++, or Obj-C.
|
||||||
|
|
||||||
### My code is detected as the wrong language
|
## Adding a language
|
||||||
|
|
||||||
This can usually be solved either by adding a new filename or file name extension to the language's entry in [`languages.yml`][languages] or adding more [samples][samples] for your language to the repository to make Linguist's classifier smarter.
|
We try only to add languages once they have some usage on GitHub. In most cases we prefer that languages be in use in hundreds of repositories before supporting them in Linguist.
|
||||||
|
|
||||||
### Syntax highlighting looks wrong
|
To add support for a new language:
|
||||||
|
|
||||||
Assuming your code is being detected as the right language (see above), in most cases this is due to a bug in the language grammar rather than a bug in Linguist. [`grammars.yml`][grammars] lists all the grammars we use for syntax highlighting on github.com. Find the one corresponding to your code's programming language and submit a bug report upstream. If you can, try to reproduce the highlighting problem in the text editor that the grammar is designed for (TextMate, Sublime Text, or Atom) and include that information in your bug report.
|
|
||||||
|
|
||||||
You can also try to fix the bug yourself and submit a Pull Request. [This piece from TextMate's documentation](http://manual.macromates.com/en/language_grammars) offers a good introduction on how to work with TextMate-compatible grammars. You can test grammars using [Lightshow](https://lightshow.githubapp.com).
|
|
||||||
|
|
||||||
Once the bug has been fixed upstream, please let us know and we'll pick it up for GitHub.
|
|
||||||
|
|
||||||
### I want to add support for the `X` programming language
|
|
||||||
|
|
||||||
Great! You'll need to:
|
|
||||||
|
|
||||||
0. Add an entry for your language to [`languages.yml`][languages].
|
0. Add an entry for your language to [`languages.yml`][languages].
|
||||||
0. Add a grammar for your language. Please only add grammars that have a license that permits redistribution.
|
0. Add a grammar for your language. Please only add grammars that have a license that permits redistribution.
|
||||||
0. Add your grammar as a submodule: `git submodule add https://github.com/JaneSmith/MyGrammar vendor/grammars/MyGrammar`.
|
0. Add your grammar as a submodule: `git submodule add https://github.com/JaneSmith/MyGrammar vendor/grammars/MyGrammar`.
|
||||||
0. Add your grammar to [`grammars.yml`][grammars] by running `script/download-grammars --add vendor/grammars/MyGrammar`.
|
0. Add your grammar to [`grammars.yml`][grammars] by running `script/download-grammars --add vendor/grammars/MyGrammar`.
|
||||||
0. Add samples for your language to the [samples directory][samples].
|
0. Add samples for your language to the [samples directory][samples] in the correct subdirectory.
|
||||||
|
0. Open a pull request, linking to a [GitHub search result](https://github.com/search?utf8=%E2%9C%93&q=extension%3Aboot+NOT+nothack&type=Code&ref=searchresults) showing in-the-wild usage.
|
||||||
|
|
||||||
We try only to add languages once they have some usage on GitHub, so please note in-the-wild usage examples in your pull request. In most cases we prefer that languages already be in use in hundreds of repositories before supporting them in Linguist.
|
## Fixing syntax highlighting
|
||||||
|
|
||||||
|
Syntax highlighting in GitHub is performed using TextMate-compatible grammars. These are the same grammars that TextMate, Sublime Text and Atom use. Every language in `languages.yml` is mapped to its corresponding TM `scope`. This scope will be used when picking up a grammar for highlighting.
|
||||||
|
|
||||||
|
Assuming your code is being detected as the right language (see [Language Detection](#language-detection) above), in most cases this is due to a bug in the language grammar rather than a bug in Linguist. [`grammars.yml`][grammars] lists all the grammars we use for syntax highlighting on github.com. Find the one corresponding to your code's programming language and submit a bug report upstream. If you can, try to reproduce the highlighting problem in the text editor that the grammar is designed for (TextMate, Sublime Text, or Atom) and include that information in your bug report.
|
||||||
|
|
||||||
|
You can also try to fix the bug yourself and submit a Pull Request. [TextMate's documentation](http://manual.macromates.com/en/language_grammars) offers a good introduction on how to work with TextMate-compatible grammars. You can test grammars using [Lightshow](https://lightshow.githubapp.com).
|
||||||
|
|
||||||
|
Once the bug has been fixed upstream, please let us know and we'll pick it up for GitHub.
|
||||||
|
|
||||||
|
## Testing
|
||||||
|
|
||||||
|
For development you are going to want to checkout out the source. To get it, clone the repo and run [Bundler](http://gembundler.com/) to install its dependencies.
|
||||||
|
|
||||||
|
git clone https://github.com/github/linguist.git
|
||||||
|
cd linguist/
|
||||||
|
script/bootstrap
|
||||||
|
|
||||||
|
To run the tests:
|
||||||
|
|
||||||
|
bundle exec rake test
|
||||||
|
|
||||||
|
Sometimes getting the tests running can be too much work, especially if you don't have much Ruby experience. It's okay: be lazy and let our build bot [Travis](http://travis-ci.org/#!/github/linguist) run the tests for you. Just open a pull request and the bot will start cranking away.
|
||||||
|
|
||||||
|
Here's our current build status: [](http://travis-ci.org/github/linguist)
|
||||||
|
|
||||||
|
## Releasing
|
||||||
|
|
||||||
|
If you are the current maintainer of this gem:
|
||||||
|
|
||||||
|
0. Create a branch for the release: `git checkout -b cut-release-vxx.xx.xx`
|
||||||
|
0. Make sure your local dependencies are up to date: `script/bootstrap`
|
||||||
|
0. Ensure that samples are updated: `bundle exec rake samples`
|
||||||
|
0. Ensure that tests are green: `bundle exec rake test`
|
||||||
|
0. Bump gem version in `lib/linguist/version.rb`, [like this](https://github.com/github/linguist/commit/8d2ea90a5ba3b2fe6e1508b7155aa4632eea2985).
|
||||||
|
0. Make a PR to github/linguist, [like this](https://github.com/github/linguist/pull/1238).
|
||||||
|
0. Build a local gem: `bundle exec rake build_gem`
|
||||||
|
0. Test the gem:
|
||||||
|
0. Bump the Gemfile and Gemfile.lock versions for an app which relies on this gem
|
||||||
|
0. Install the new gem locally
|
||||||
|
0. Test behavior locally, branch deploy, whatever needs to happen
|
||||||
|
0. Merge github/linguist PR
|
||||||
|
0. Tag and push: `git tag vx.xx.xx; git push --tags`
|
||||||
|
0. Push to rubygems.org -- `gem push github-linguist-3.0.0.gem`
|
||||||
|
|
||||||
[grammars]: /grammars.yml
|
[grammars]: /grammars.yml
|
||||||
[languages]: /lib/linguist/languages.yml
|
[languages]: /lib/linguist/languages.yml
|
||||||
[samples]: /samples
|
[samples]: /samples
|
||||||
|
[new-issue]: https://github.com/github/linguist/issues/new
|
||||||
|
|||||||
184
README.md
184
README.md
@@ -1,196 +1,38 @@
|
|||||||
# Linguist
|
# Linguist
|
||||||
|
|
||||||
We use this library at GitHub to detect blob languages, ignore binary files, suppress generated files in diffs, and generate language breakdown graphs.
|
This library is used on GitHub.com to detect blob languages, ignore binary or vendored files, suppress generated files in diffs, and generate language breakdown graphs.
|
||||||
|
|
||||||
Tips for filing issues and creating pull requests can be found in [`CONTRIBUTING.md`](/CONTRIBUTING.md).
|
See [Troubleshooting](#troubleshooting) and [`CONTRIBUTING.md`](/CONTRIBUTING.md) before filing an issue or creating a pull request.
|
||||||
|
|
||||||
## Features
|
## Troubleshooting
|
||||||
|
|
||||||
### Language detection
|
### My repository is detected as the wrong language
|
||||||
|
|
||||||
Linguist defines a list of all languages known to GitHub in a [yaml file](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
|
|
||||||
|
|
||||||
Most languages are detected by their file extension. For disambiguating between files with common extensions, we first apply some common-sense heuristics to pick out obvious languages. After that, we use a
|
The Language stats bar is built by aggregating the languages of each file in that repository. If it is reporting a language that you don't expect, click on the name of the language and to see a list of the files that are identified as that language. If there are files in your repository
|
||||||
[statistical
|
|
||||||
classifier](https://github.com/github/linguist/blob/master/lib/linguist/classifier.rb).
|
|
||||||
This process can help us tell the difference between, for example, `.h` files which could be either C, C++, or Obj-C.
|
|
||||||
|
|
||||||
```ruby
|
consider moving the files into one of the
|
||||||
|
|
||||||
Linguist::FileBlob.new("lib/linguist.rb").language.name #=> "Ruby"
|
See [Overrides](#overrides)
|
||||||
|
|
||||||
Linguist::FileBlob.new("bin/linguist").language.name #=> "Ruby"
|
|
||||||
```
|
|
||||||
|
|
||||||
See [lib/linguist/language.rb](https://github.com/github/linguist/blob/master/lib/linguist/language.rb) and [lib/linguist/languages.yml](https://github.com/github/linguist/blob/master/lib/linguist/languages.yml).
|
|
||||||
|
|
||||||
### Syntax Highlighting
|
|
||||||
|
|
||||||
Syntax highlighting in GitHub is performed using TextMate-compatible grammars. These are the same grammars that TextMate, Sublime Text and Atom use.
|
|
||||||
|
|
||||||
Every language in `languages.yml` is mapped to its corresponding TM `scope`. This scope will be used when picking up a grammar for highlighting. **When adding a new language to Linguist, please add its corresponding scope too (assuming there's an existing TextMate bundle, Sublime Text package, or Atom package) so syntax highlighting works for it**.
|
|
||||||
|
|
||||||
### Stats
|
|
||||||
|
|
||||||
The Language stats bar that you see on every repository is built by aggregating the languages of each file in that repository. The top language in the graph determines the project's primary language.
|
|
||||||
|
|
||||||
The repository stats API, accessed through `#languages`, can be used on a directory:
|
|
||||||
|
|
||||||
***API UPDATE***
|
|
||||||
|
|
||||||
Since [Version 3.0.0](https://github.com/github/linguist/releases/tag/v3.0.0) Linguist expects a git repository (in the form of a [Rugged::Repository](https://github.com/libgit2/rugged#repositories)) to be passed when initializing `Linguist::Repository`.
|
|
||||||
|
|
||||||
|
|
||||||
```ruby
|
|
||||||
require 'rugged'
|
|
||||||
require 'linguist'
|
|
||||||
|
|
||||||
repo = Rugged::Repository.new('.')
|
|
||||||
project = Linguist::Repository.new(repo, repo.head.target_id)
|
|
||||||
project.language #=> "Ruby"
|
|
||||||
project.languages #=> { "Ruby" => 119387 }
|
|
||||||
```
|
|
||||||
|
|
||||||
These stats are also printed out by the `linguist` binary. You can use the
|
|
||||||
`--breakdown` flag, and the binary will also output the breakdown of files by language.
|
|
||||||
|
|
||||||
You can try running `linguist` on the root directory in this repository itself:
|
|
||||||
|
|
||||||
$ bundle exec linguist --breakdown
|
|
||||||
|
|
||||||
100.00% Ruby
|
|
||||||
|
|
||||||
Ruby:
|
|
||||||
Gemfile
|
|
||||||
Rakefile
|
|
||||||
bin/linguist
|
|
||||||
github-linguist.gemspec
|
|
||||||
lib/linguist.rb
|
|
||||||
lib/linguist/blob_helper.rb
|
|
||||||
lib/linguist/classifier.rb
|
|
||||||
lib/linguist/file_blob.rb
|
|
||||||
lib/linguist/generated.rb
|
|
||||||
lib/linguist/heuristics.rb
|
|
||||||
lib/linguist/language.rb
|
|
||||||
lib/linguist/lazy_blob.rb
|
|
||||||
lib/linguist/md5.rb
|
|
||||||
lib/linguist/repository.rb
|
|
||||||
lib/linguist/samples.rb
|
|
||||||
lib/linguist/tokenizer.rb
|
|
||||||
lib/linguist/version.rb
|
|
||||||
test/test_blob.rb
|
|
||||||
test/test_classifier.rb
|
|
||||||
test/test_heuristics.rb
|
|
||||||
test/test_language.rb
|
|
||||||
test/test_md5.rb
|
|
||||||
test/test_pedantic.rb
|
|
||||||
test/test_repository.rb
|
|
||||||
test/test_samples.rb
|
|
||||||
test/test_tokenizer.rb
|
|
||||||
|
|
||||||
#### Ignore vendored files
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
```ruby
|
|
||||||
Linguist::FileBlob.new("vendor/plugins/foo.rb").vendored? # => true
|
|
||||||
```
|
|
||||||
|
|
||||||
See [Linguist::BlobHelper#vendored?](https://github.com/github/linguist/blob/master/lib/linguist/blob_helper.rb) and [lib/linguist/vendor.yml](https://github.com/github/linguist/blob/master/lib/linguist/vendor.yml).
|
|
||||||
|
|
||||||
#### Generated file detection
|
|
||||||
|
|
||||||
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.
|
|
||||||
|
|
||||||
```ruby
|
|
||||||
Linguist::FileBlob.new("underscore.min.js").generated? # => true
|
|
||||||
```
|
|
||||||
|
|
||||||
See [Linguist::Generated#generated?](https://github.com/github/linguist/blob/master/lib/linguist/generated.rb).
|
|
||||||
|
|
||||||
## Overrides
|
## Overrides
|
||||||
|
|
||||||
Linguist supports custom overrides for language definitions and vendored paths. Add a `.gitattributes` file to your project using the keys `linguist-language` and `linguist-vendored` with the standard git-style path matchers for the files you want to override.
|
Linguist supports custom overrides for language definitions and vendored paths. Please note that the overrides currently only affect the language statistics for a repository and not the syntax-highlighting of files.
|
||||||
|
|
||||||
Please note that the overrides currently only affect the language statistics for a repository and not the syntax-highlighting of files.
|
Commit a `.gitattributes` file to your project and use standard git-style path matchers for the files you want to override to set `linguist-language` and `linguist-vendored`.
|
||||||
|
|
||||||
```
|
```
|
||||||
$ cat .gitattributes
|
$ cat .gitattributes
|
||||||
*.rb linguist-language=Java
|
*.rb linguist-language=Java
|
||||||
|
|
||||||
$ linguist --breakdown
|
|
||||||
100.00% Java
|
|
||||||
|
|
||||||
Java:
|
|
||||||
ruby_file.rb
|
|
||||||
```
|
```
|
||||||
|
|
||||||
By default, Linguist treats all of the paths defined in [lib/linguist/vendor.yml](https://github.com/github/linguist/blob/master/lib/linguist/vendor.yml) as vendored and therefore doesn't include them in the language statistics for a repository. Use the `linguist-vendored` attribute to vendor or un-vendor paths.
|
Checking code you didn't write, such as JavaScript libraries, 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. By default, Linguist treats all of the paths defined in [lib/linguist/vendor.yml](https://github.com/github/linguist/blob/master/lib/linguist/vendor.yml) as vendored and therefore doesn't include them in the language statistics for a repository.
|
||||||
|
|
||||||
|
Use the `linguist-vendored` attribute to vendor or un-vendor paths.
|
||||||
|
|
||||||
```
|
```
|
||||||
$ cat .gitattributes
|
$ cat .gitattributes
|
||||||
special-vendored-path/* linguist-vendored
|
special-vendored-path/* linguist-vendored
|
||||||
jquery.js linguist-vendored=false
|
jquery.js linguist-vendored=false
|
||||||
```
|
```
|
||||||
|
|
||||||
## Installation
|
|
||||||
|
|
||||||
Github.com is usually running the latest version of the `github-linguist` gem that is released on [RubyGems.org](http://rubygems.org/gems/github-linguist).
|
|
||||||
|
|
||||||
But for development you are going to want to checkout out the source. To get it, clone the repo and run [Bundler](http://gembundler.com/) to install its dependencies.
|
|
||||||
|
|
||||||
git clone https://github.com/github/linguist.git
|
|
||||||
cd linguist/
|
|
||||||
script/bootstrap
|
|
||||||
|
|
||||||
To run the tests:
|
|
||||||
|
|
||||||
bundle exec rake test
|
|
||||||
|
|
||||||
### A note on language extensions
|
|
||||||
|
|
||||||
Linguist has a number of methods available to it for identifying the language of a particular file. The initial lookup is based upon the extension of the file, possible file extensions are defined in an array called `extensions`. Take a look at this example for example for `Perl`:
|
|
||||||
|
|
||||||
```
|
|
||||||
Perl:
|
|
||||||
type: programming
|
|
||||||
ace_mode: perl
|
|
||||||
color: "#0298c3"
|
|
||||||
extensions:
|
|
||||||
- .pl
|
|
||||||
- .PL
|
|
||||||
- .perl
|
|
||||||
- .ph
|
|
||||||
- .plx
|
|
||||||
- .pm
|
|
||||||
- .pod
|
|
||||||
- .psgi
|
|
||||||
interpreters:
|
|
||||||
- perl
|
|
||||||
```
|
|
||||||
Any of the extensions defined are valid but the first in this array should be the most popular.
|
|
||||||
|
|
||||||
### Testing
|
|
||||||
|
|
||||||
Sometimes getting the tests running can be too much work, especially if you don't have much Ruby experience. It's okay: be lazy and let our build bot [Travis](http://travis-ci.org/#!/github/linguist) run the tests for you. Just open a pull request and the bot will start cranking away.
|
|
||||||
|
|
||||||
Here's our current build status, which is hopefully green: [](http://travis-ci.org/github/linguist)
|
|
||||||
|
|
||||||
### Releasing
|
|
||||||
|
|
||||||
If you are the current maintainer of this gem:
|
|
||||||
|
|
||||||
0. Create a branch for the release: `git checkout -b cut-release-vxx.xx.xx`
|
|
||||||
0. Make sure your local dependencies are up to date: `script/bootstrap`
|
|
||||||
0. Ensure that samples are updated: `bundle exec rake samples`
|
|
||||||
0. Ensure that tests are green: `bundle exec rake test`
|
|
||||||
0. Bump gem version in `lib/linguist/version.rb`. For example, [like this](https://github.com/github/linguist/commit/8d2ea90a5ba3b2fe6e1508b7155aa4632eea2985).
|
|
||||||
0. Make a PR to github/linguist. For example, [#1238](https://github.com/github/linguist/pull/1238).
|
|
||||||
0. Build a local gem: `bundle exec rake build_gem`
|
|
||||||
0. Testing:
|
|
||||||
0. Bump the Gemfile and Gemfile.lock versions for an app which relies on this gem
|
|
||||||
0. Install the new gem locally
|
|
||||||
0. Test behavior locally, branch deploy, whatever needs to happen
|
|
||||||
0. Merge github/linguist PR
|
|
||||||
0. Tag and push: `git tag vx.xx.xx; git push --tags`
|
|
||||||
0. Push to rubygems.org -- `gem push github-linguist-3.0.0.gem`
|
|
||||||
|
|||||||
Reference in New Issue
Block a user