Download the PHP package cerealkiller97/filament-bug-reports without Composer

On this page you can find all versions of the php package cerealkiller97/filament-bug-reports. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of cerealkiller97/filament-bug-reports

Informations about the package filament-bug-reports

Filament Bug Reports

Packagist Release Tests PHPStan Type coverage

Get instant feedback from the people actually using your app. Collect bug reports from inside your Filament panel, and push the ones you confirm are real straight to GitHub as issues.

Feedback arrives the moment a user hits the problem — not days later through a support email, a Slack thread, or a screenshot with no context. Your users get a Report a bug button in the panel's topbar and a short, plain-language form — no Markdown, no issue templates, no GitHub account. You get a triage table where a single click turns a report into a proper GitHub issue, and the issue's state (open/closed) is mirrored back onto the report automatically.

📖 Read the documentation

Dark Light

How it works

  1. Anyone in the panel reports a bug. They describe the problem, list the steps that led to it, and optionally attach a screenshot. The report is stamped with the reporter, their role and the running app version — they aren't asked for any of it.
  2. A manager triages. Reports land in a table only managers can see. Noise gets deleted; the real ones get Mark as real.
  3. A GitHub issue is created, with the steps and screenshot formatted into the body. The issue number and URL are stored on the report.
  4. State syncs back. An hourly command checks each linked issue: closed becomes Resolved, reopened flips back to In progress.

Requirements

Installation

Publish and run the migration:

Optionally publish the config file:

Then register the plugin on the panel you want it in:

That single authorizeManagementUsing call matters: management defaults to nobody. Until you opt someone in, no one can see the report list — though everyone can still file a report.

Finally, point it at a repository with a token that has the repo (or issues:write) scope:

See the installation guide for the rest.

Documentation
Authorization Who can file a report, and who can triage one.
Reporting a bug The topbar button and the form behind it.
The triage table The stats, the grouping, and marking a report as real.
The GitHub issue What the created issue looks like, and which options GitHub honours.
Keeping reports in sync Mirroring issue state back onto the report.
Configuration Every key in config/bug-reports.php.
Translations Changing the wording.

Testing

Contributing

Pull requests are welcome — bug fixes, new features, better docs, or just a typo you spotted. See the contributing guide for the workflow, and open the PR even if you're unsure about it.

License

Apache License 2.0. See LICENSE.md.

Proudly made by Stefan Bogdanovic.

All versions of filament-bug-reports with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
filament/filament Version ^5.0
illuminate/contracts Version ^13.0
spatie/laravel-package-tools Version ^1.16
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package cerealkiller97/filament-bug-reports contains the following files

Loading the files please wait ...