https://github.com/laravel-notification-channels/skeleton
https://github.com/laravel-notification-channels/skeleton
hacktoberfest
Last synced: 8 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/laravel-notification-channels/skeleton
- Owner: laravel-notification-channels
- License: mit
- Created: 2016-08-11T07:14:01.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2024-04-18T23:09:48.000Z (over 1 year ago)
- Last Synced: 2025-03-29T03:32:12.190Z (9 months ago)
- Topics: hacktoberfest
- Language: PHP
- Homepage:
- Size: 31.3 KB
- Stars: 51
- Watchers: 5
- Forks: 59
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.md
Awesome Lists containing this project
README
Please see [this repo](https://github.com/laravel-notification-channels/channels) for instructions on how to submit a channel proposal.
# A Boilerplate repo for contributions
[](https://packagist.org/packages/laravel-notification-channels/:package_name)
[](LICENSE.md)
[](https://travis-ci.org/laravel-notification-channels/:package_name)
[](https://styleci.io/repos/:style_ci_id)
[](https://insight.sensiolabs.com/projects/:sensio_labs_id)
[](https://scrutinizer-ci.com/g/laravel-notification-channels/:package_name)
[](https://scrutinizer-ci.com/g/laravel-notification-channels/:package_name/?branch=master)
[](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 10.x.
**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.
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.
## Contents
- [Installation](#installation)
- [Setting up the :service_name service](#setting-up-the-:service_name-service)
- [Usage](#usage)
- [Available Message methods](#available-message-methods)
- [Changelog](#changelog)
- [Testing](#testing)
- [Security](#security)
- [Contributing](#contributing)
- [Credits](#credits)
- [License](#license)
## Installation
Please also include the steps for any third-party service setup that's required for this package.
### Setting up the :service_name service
Optionally include a few steps how users can set up the service.
## Usage
Some code examples, make it clear how to use the package
### Available Message methods
A list of all available options
## Changelog
Please see [CHANGELOG](CHANGELOG.md) for more information what has changed recently.
## Testing
``` bash
$ composer test
```
## Security
If you discover any security related issues, please email :author_email instead of using the issue tracker.
## Contributing
Please see [CONTRIBUTING](CONTRIBUTING.md) for details.
## Credits
- [:author_name](https://github.com/:author_username)
- [All Contributors](../../contributors)
## License
The MIT License (MIT). Please see [License File](LICENSE.md) for more information.