Tree: e26bd05ede

babel-plugin-for-integration-tests

browser-recipe

browser-support

export-module

failure-output

faster-string-diff

fix-readme-improvements

fix-string-diff-colours

hoisting-throws-helper

master

refactor-reporters

replace-snapshot

safe-default-concurrency

upgrade-xo

use-hullabaloo

v0.1.0

v0.10.0

v0.11.0

v0.12.0

v0.13.0

v0.14.0

v0.15.0

v0.15.1

v0.15.2

v0.16.0

v0.17.0

v0.18.0

v0.18.1

v0.18.2

v0.2.0

v0.3.0

v0.4.0

v0.4.1

v0.4.2

v0.5.0

v0.6.0

v0.6.1

v0.7.0

v0.8.0

v0.9.0

v0.9.1

v0.9.2

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'e26bd05ede'

${ noResults }

Commit Graph

10 Commits (e26bd05edef35238214676b3e7d2d2d8ec8a65e1)

Author	SHA1	Message	Date
Sindre Sorhus	bdb8b6ebaa	allow Node.js 0.10 to fail on Travis until we track down #498	9 years ago
Sindre Sorhus	0e6db13a91	minor doc and style tweaks	9 years ago
Stephen Edgar	345700e974	Travis CI: Switch from deprecated `stable` NodeJS version to v4.x.x and v5.x.x	9 years ago
James Talmage	9e6d9724d5	Close #333 PR: Upgrade to Babel 6.	9 years ago
James Talmage	1816f73b9b	Fix failing coveralls script. For PR's `process.env.COVERALLS_REPO_TOKEN` does not exist, so `tap` will not automatically send data to coveralls. Hence our existing script: `npm run coveralls`. Unfortuneately that seems to create problems to create problems when merged onto master. In that case `tap` **will** automatically push our coverage data, and the follow up push seems to fail. To fix all this, I check the environment variable in .travis.yaml, and manually push the coverage data if the environment variable does not exist. https://travis-ci.org/sindresorhus/ava/jobs/92855751	9 years ago
Sindre Sorhus	20a704abd3	add code coverage with coveralls	9 years ago
Sindre Sorhus	6a6b757031	tweaks	9 years ago
Sindre Sorhus	f3c12c1e4c	add XO	9 years ago
Sindre Sorhus	6ca22cbe2d	Update .travis.yml	10 years ago
Sindre Sorhus	1089a87c2c	init	10 years ago