benmvp
/
react-composite-events
/
41
100%
|
Ran
|
Jobs
6
|
Files
1
|
Run time
2min
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
benmvp<a href="https://github.com/benmvp/react-composite-events/commit/<a class=hub.com/benmvp/react-composite-events/commit/b6e4cd6b9cf14749a9f7e1fbc6e6662fc4e8f9f5">b6e4cd6b9<a href="https://github.com/benmvp/react-composite-events/commit/b6e4cd6b9cf14749a9f7e1fbc6e6662fc4e8f9f5">">ci: Try using deploy script again With </a><a class="double-link" href="https://github.com/benmvp/react-composite-events/commit/<a class="double-link" href="https://github.com/benmvp/react-composite-events/commit/34bebb91c5c4b659846c125d935d8545693024cf">34bebb91c</a>">34bebb91c</a><a href="https://github.com/benmvp/react-composite-events/commit/b6e4cd6b9cf14749a9f7e1fbc6e6662fc4e8f9f5"> I moved the release script into `after_success` which worked and released v1! But ideally the release script will be in the deploy script so that we can return to running tests on multiple node versions. Trying to move it back to the deploy script, but keep the `yarn global add` in `after_success`. Also: - Adding dummy CHANGELOG.md for when the lib is released. It points to releases Github page - Updating README to list ESM modules first
42 of 42 branches covered (100.0%)
Branch coverage included in aggregate %.
51 of 51 relevant lines covered (100.0%)
251.18 hits per line
Jobs
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 41.1 | 1 |
100.0 |
Travis Job 41.1 | |
| 2 | 41.2 | 1 |
100.0 |
Travis Job 41.2 | |
| 3 | 41.3 | 1 |
100.0 |
Travis Job 41.3 | |
| 4 | 41.4 | 1 |
100.0 |
Travis Job 41.4 | |
| 5 | 41.5 | 1 |
100.0 |
Travis Job 41.5 | |
| 6 | 41.6 | 1 |
100.0 |
Travis Job 41.6 |
Source Files on build 41
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|