Download the PHP package mydnic/changelog-commit-for-laravel without Composer
On this page you can find all versions of the php package mydnic/changelog-commit-for-laravel. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download mydnic/changelog-commit-for-laravel
More information about mydnic/changelog-commit-for-laravel
Files in mydnic/changelog-commit-for-laravel
Package changelog-commit-for-laravel
Short Description Automatically generate a changelog inside your Laravel App based on your commit descriptions
License MIT
Homepage https://github.com/mydnic/changelog-commit-for-laravel
Informations about the package changelog-commit-for-laravel
Automatic Changelog Generator for Laravel Applications
Automatically generate a changelog for your users inside your Laravel App based on your commit descriptions.
Introduction
When building a web project, it's important to let your users know what changed in each release, or even as soon as a bug is fixed. You might do that through a blog post, or on social media, but it's still a manual process.
This package will automatically generate a changelog based on your commit descriptions. It will fetch the commit history from your repository and store the messages from your commit descriptions in a database table.
You can then display the changelog in your app, or even send it to your users via email.
Installation
You can install the package via composer:
You can publish and run the migrations with:
You can publish the config file with:
This is the contents of the published config file:
Usage
Once the package is installed on your project, you should add the changelod:fetch
command to your deployment process.
Now, every time your application is deployed, the changelog will be updated with the latest commit messages.
Write your commit messages
Here's an example of a commit message:
As you can see, the commit message is composed of several lines. The first line is your usual commit message. The other lines can be used to add more details about the commit.
But only the other lines starting with >
will be used to generate the changelog.
Generate the changelog
After you've pushed your commits, you can run the following command to fetch the commit history. Or you can add this command to your deployment process so you don't have to run it manually.
This will fetch the commit history from your repository and store the messages (all lines starting with >
) from your commit descriptions in a database table.
Showing the changelog
You can then display the changelog in your app, or even send it to your users via email.
Here's an example of how to display the changelog in your app:
Use the Changelog
model to fetch the changelog entries in your application.
Front End Examples
Please submit more examples if you have any!
VueJS Component
Testing
Changelog
Please see CHANGELOG for more information on what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Security Vulnerabilities
Please review our security policy on how to report security vulnerabilities.
Credits
- Clément Rigo
- All Contributors
License
The MIT License (MIT). Please see License File for more information.
All versions of changelog-commit-for-laravel with dependencies
spatie/laravel-package-tools Version ^1.16
illuminate/contracts Version >=10.0