Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Symfony Debug Toolbar Git

Symfony Debug Toolbar Git Laravel Package

kendrick/symfony-debug-toolbar-git

Adds Git context to the Symfony debug toolbar, showing the current branch, commit hash, and working tree status right in your development toolbar so you can confirm which code version you're testing without leaving the browser.

View on GitHub
Deep Wiki
Context7

Git information into Symfony Debug Toolbar

Frequently asked questions about Symfony Debug Toolbar Git
Is kendrick/symfony-debug-toolbar-git compatible with Laravel?
No. It is a Symfony bundle that hooks into Symfony's WebProfilerBundle toolbar; Laravel does not boot Symfony bundles or mount that toolbar in its request lifecycle. Installing it in a Laravel app would pull in bundle classes that never run. For Laravel, use barryvdh/laravel-debugbar or a custom collector instead.
How do I install kendrick/symfony-debug-toolbar-git?
It is installed with Composer as kendrick/symfony-debug-toolbar-git and registered as a Symfony bundle, typically in config/bundles.php. It has no Laravel service provider or auto-discovery for Laravel. Because the last release targets Symfony 3.4/4.0 and PHP 7.x, installation on modern Symfony or PHP versions is likely to fail or break at render time.
What Laravel versions does this package support?
None. The package is not a Laravel package and has no Laravel service provider, facade, config file, or Debugbar collector. Its integration surface is Symfony's data_collector tag and WebProfiler Twig templates. There is no supported Laravel version.
Can I use this package with barryvdh/laravel-debugbar?
No, they use different collector contracts and renderers. barryvdh/laravel-debugbar expects collectors implementing its own DataCollector interface, while this bundle registers a Symfony data_collector and injects into the Symfony toolbar. You cannot drop this bundle's collector into Laravel Debugbar without rewriting it. The practical path is to write a small custom Laravel Debugbar collector that returns branch and commit data.
How do I show Git branch and commit hash in Laravel Debugbar?
Implement a custom collector for barryvdh/laravel-debugbar that runs git log -1 or reads build-time environment variables, then exposes branch, hash, author, and message as an array. Cache the result per process or request and guard it with app()->isLocal() so production never shells out to git. This replicates the concept of kendrick/symfony-debug-toolbar-git without adopting its abandoned Symfony code.
Does this package work with Symfony 5 or Symfony 6?
Likely not without changes. The package's last release was in January 2018 and targets the Symfony 3.4/4.0 era with PHP 7.x. WebProfilerBundle Twig template inheritance and toolbar layout changed materially in Symfony 5 and 6, so the panel render is expected to break. A fork would need its Twig template reimplemented against the current WebProfiler layout.
Is kendrick/symfony-debug-toolbar-git maintained?
No active maintenance is evident. The last release was 2018-01-08, it has around 30 stars and zero dependents, and there is no visible CI or test coverage. It is a single-maintainer package with no downstream code exercised in production. Treat it as abandoned and avoid adding it to a new Laravel or Symfony codebase.
What are the alternatives to kendrick/symfony-debug-toolbar-git for Laravel?
For Laravel, the main alternative is barryvdh/laravel-debugbar with a custom Git collector, or simply exposing GIT_COMMIT, GIT_BRANCH, and GIT_COMMIT_MESSAGE as environment variables from CI. A Blade partial or the Debugbar messages/variables panel can display those values. Both options are safer than adopting an abandoned Symfony bundle.
Will this package work in production or CI?
It is a development toolbar extension and is not intended for production. It shells out to git log -1 during a request, which assumes a .git directory and a git binary are present; typical production container images ship neither. For staging or production build identity, inject commit metadata as environment variables at deploy time instead of running git per request.
How do I configure or test the Git toolbar panel?
The package advertises zero-config integration for Symfony apps, so configuration is minimal: register the bundle and ensure the app runs in a Git working tree with the git binary available. There is no documented test suite, so you would need to add your own tests around any fork. In Laravel, testing a custom collector is straightforward with Laravel Debugbar's collector interface and a faked git output.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
novasa/laravel-language-center
opencage/geocode
adolfoholzer/parameters
livenetworks/ln-starter
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core