<commit_before>
#### Install travis
Create an account on https://travis-ci.org/ and login  


(need ruby 2.0)  
more information https://github.com/travis-ci/travis.rb#installation  
`gem install travis -v 1.8.2 --no-rdoc --no-ri`  
`sudo gem install travis`  

`travis version`  
"Shell completion not installed. Would you like to install it now? |y| y"  

should be 1.8.2



#### create a travis config 'travis.yml'
create .travis.yml (not ignored)  
The "addons" sections is need when your app uses bcrypt.  

```
language: node_js
node_js:
  - '4'
services:
  - mongodb
addons:
  apt:
    sources:
      - ubuntu-toolchain-r-test
    packages:
      - gcc-4.8
      - g++-4.8
env:
  - CXX=g++-4.8
sudo: required
before_script: npm install
script:
  - npm run test
  - npm run lint
```
`travis lint`   checks that your travis file is OK  
"Hooray, .travis.yml looks valid :)"

#### Login
`travis login`  use github login  


#### Enable travis for this repo
`travis enable`  
"detected repository is xxxx, is this correct yes|no
triggering sync"  


`travis open`   like heroku open - if you're logged in to the browser you'll get to this repo

You can add status image to your README.md - will tell if you're passing tests on most recent push
click on "unknown" next to "build" and choose markdown 9:22<commit_msg>add known issue with travis lint comment<commit_after>
#### Install travis
Create an account on https://travis-ci.org/ and login  


(need ruby 2.0)  
more information https://github.com/travis-ci/travis.rb#installation  
`gem install travis -v 1.8.2 --no-rdoc --no-ri`  
`sudo gem install travis`  

`travis version`  
"Shell completion not installed. Would you like to install it now? |y| y"  

should be 1.8.2



#### create a travis config 'travis.yml'
create .travis.yml (not ignored)  
The "addons" sections is need when your app uses bcrypt.  

```
language: node_js
node_js:
  - '4'
services:
  - mongodb
addons:
  apt:
    sources:
      - ubuntu-toolchain-r-test
    packages:
      - gcc-4.8
      - g++-4.8
env:
  - CXX=g++-4.8
sudo: required
before_script: npm install
script:
  - npm run test
  - npm run lint
```
`travis lint`   checks that your travis file is OK  
"Hooray, .travis.yml looks valid :)"  

known issue with travis lint when you have addons:  
https://github.com/travis-ci/travis-ci/issues/3694

#### Login
`travis login`  use github login  


#### Enable travis for this repo
`travis enable`  
"detected repository is xxxx, is this correct yes|no
triggering sync"  


`travis open`   like heroku open - if you're logged in to the browser you'll get to this repo

You can add status image to your README.md - will tell if you're passing tests on most recent push
click on "unknown" next to "build" and choose markdown 9:22
{'fraction_non_alphanumeric': 0.10577617328519856, 'fraction_numerical': 0.01444043321299639, 'mean_word_length': 3.105185185185185, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 5, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4567806', 'n_tokens_mistral': 999, 'n_tokens_neox': 962, 'n_words': 359}