Weave Code
Commit History Bundle Laravel Package
spiriitlabs/commit-history-bundle
SpiriitLabs Commit History Bundle adds a simple Symfony interface for browsing your project's Git commit history. View commits, authors, dates, and messages directly in your app, making release notes and change tracking easier without leaving the admin.
SpiriitLabs Commit History Bundle brings your repository’s commit history into a Symfony application, making recent changes easy to review without leaving the project. It offers a lightweight, configurable way to expose commit data for internal dashboards, audits, or release tracking.
- Standard Symfony bundle integration
- Browse commit messages, authors, and dates
- Simple configuration for repository/history settings
- Lightweight setup for internal tooling
- Useful for release and change visibility
Frequently asked questions about Commit History Bundle
- Is spiriitlabs/commit-history-bundle a Laravel package?
- No, it is a Symfony bundle, not a native Laravel package. It displays Git commit history as a vertical timeline inside a Symfony application. Laravel uses different package discovery and service-provider conventions, so do not expect a drop-in install.
- How do I install spiriitlabs/commit-history-bundle?
- Install it with Composer using spiriitlabs/commit-history-bundle, then enable the bundle in your Symfony application. With Symfony Flex, bundle registration is usually handled through config/bundles.php. Check the README for the exact bundle class and Symfony version constraints.
- What does this bundle actually display?
- It reads your project Git commit history and renders it as a vertical timeline. The timeline is intended to show recent commits, messages, authors, and timestamps. It is useful for admins and teams who want quick release context inside the dashboard.
- Can I use spiriitlabs/commit-history-bundle in a Laravel app?
- Not directly, because it is built as a Symfony bundle and relies on Symfony bundle and kernel integration. Laravel does not load Symfony bundles the same way. You could study the source or extract the Git-reading logic, but it is not supported as a Laravel package.
- Which Symfony versions are supported?
- The provided context does not list exact Symfony version support. Check the repository composer.json and README for the current Symfony framework and bundle constraints. Verify compatibility before upgrading Symfony or installing in an older project.
- How should I secure the commit history timeline?
- Put the timeline route behind your Symfony firewall and restrict it to trusted roles such as ROLE_ADMIN. Commit messages can contain sensitive project details, so avoid exposing the timeline publicly. Check the bundle documentation for route and configuration options.
- Does this bundle work in production?
- It can work in production only if the application runtime can access the Git repository and, depending on implementation, the git executable. Production containers often use shallow clones or no repository at all, so test that setup first. Also restrict access so commit metadata is not exposed to unauthorized users.
- How do I test the commit history timeline?
- Test it in a Symfony application where a Git repository is available to the runtime. Use a functional test that authenticates as an authorized admin and requests the timeline route. If possible, mock or fixture the Git output so tests do not depend on local commit history.
- What are alternatives for Laravel developers who want commit history in the dashboard?
- For Laravel, prefer a Laravel-specific package or a small custom controller or Artisan command that reads git log output. You can also link to your Git hosting provider for full history instead of embedding it. This Symfony bundle is not the native choice for Laravel applications.
- Is spiriitlabs/commit-history-bundle actively maintained?
- Check the GitHub repository and Packagist page for the latest release, recent commits, and open issues. The provided context does not include maintenance status. Review activity and compatibility before relying on it for production dashboards.
Weaver
How can I help you explore Laravel packages today?