Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Add code coverage and badges
  • Loading branch information
casperboone authored and freekmurze committed Aug 16, 2016
1 parent 64c3ac5 commit fbed03e
Show file tree
Hide file tree
Showing 3 changed files with 14 additions and 2 deletions.
2 changes: 2 additions & 0 deletions .scrutinizer.yml
Expand Up @@ -17,3 +17,5 @@ checks:
fix_identation_4spaces: true fix_identation_4spaces: true
fix_doc_comments: true fix_doc_comments: true


tools:
external_code_coverage: true
3 changes: 2 additions & 1 deletion .travis.yml
Expand Up @@ -18,4 +18,5 @@ script:
- phpunit --coverage-text --coverage-clover=coverage.clover - phpunit --coverage-text --coverage-clover=coverage.clover


after_script: after_script:
- php vendor/bin/ocular code-coverage:upload --format=php-clover coverage.clover - wget https://scrutinizer-ci.com/ocular.phar
- php ocular.phar code-coverage:upload --format=php-clover coverage.clover
11 changes: 10 additions & 1 deletion README.md
Expand Up @@ -6,9 +6,18 @@ https://laravel.com/docs/master/notifications


# A Boilerplate repo for contributions # A Boilerplate repo for contributions


[![Latest Version on Packagist](https://img.shields.io/packagist/v/laravel-notification-channels/:package_name.svg?style=flat-square)](https://packagist.org/packages/laravel-notification-channels/:package_name)
[![Software License](https://img.shields.io/badge/license-MIT-brightgreen.svg?style=flat-square)](LICENSE.md)
[![Build Status](https://img.shields.io/travis/laravel-notification-channels/:package_name/master.svg?style=flat-square)](https://travis-ci.org/laravel-notification-channels/:package_name)
[![StyleCI](https://styleci.io/repos/:style_ci_id/shield)](https://styleci.io/repos/:style_ci_id)
[![SensioLabsInsight](https://img.shields.io/sensiolabs/i/:sensio_labs_id.svg?style=flat-square)](https://insight.sensiolabs.com/projects/:sensio_labs_id)
[![Quality Score](https://img.shields.io/scrutinizer/g/laravel-notification-channels/:package_name.svg?style=flat-square)](https://scrutinizer-ci.com/g/laravel-notification-channels/:package_name)
[![Code Coverage](https://img.shields.io/scrutinizer/coverage/g/laravel-notification-channels/:package_name/master.svg?style=flat-square)](https://scrutinizer-ci.com/g/laravel-notification-channels/:package_name/?branch=master)
[![Total Downloads](https://img.shields.io/packagist/dt/laravel-notification-channels/:package_name.svg?style=flat-square)](https://packagist.org/packages/laravel-notification-channels/:package_name)

This package makes it easy to send notifications using [:service_name](link to service) with Laravel 5.3. This package makes it easy to send notifications using [:service_name](link to service) with Laravel 5.3.


**Note:** Replace ```:channel_namespace``` ```:service_name``` ```:author_name``` ```:author_username``` ```:author_website``` ```:author_email``` ```:package_name``` ```:package_description``` with their correct values in [README.md](README.md), [CHANGELOG.md](CHANGELOG.md), [CONTRIBUTING.md](CONTRIBUTING.md), [LICENSE.md](LICENSE.md), [composer.json](composer.json) and other files, then delete this line. **Note:** Replace ```:channel_namespace``` ```:service_name``` ```:author_name``` ```:author_username``` ```:author_website``` ```:author_email``` ```:package_name``` ```:package_description``` ```:style_ci_id``` ```:sensio_labs_id``` with their correct values in [README.md](README.md), [CHANGELOG.md](CHANGELOG.md), [CONTRIBUTING.md](CONTRIBUTING.md), [LICENSE.md](LICENSE.md), [composer.json](composer.json) and other files, then delete this line.
**Tip:** Use "Find in Path/Files" in your code editor to find these keywords within the package directory and replace all occurences with your specified term. **Tip:** Use "Find in Path/Files" in your code editor to find these keywords within the package directory and replace all occurences with your specified term.


This is where your description should go. Add a little code example so build can understand real quick how the package can be used. Try and limit it to a paragraph or two. This is where your description should go. Add a little code example so build can understand real quick how the package can be used. Try and limit it to a paragraph or two.
Expand Down

0 comments on commit fbed03e

Please sign in to comment.