Weave Code
Filament Cms Github Laravel Package
tomatophp/filament-cms-github
Filament CMS GitHub integration for managing repository-backed content from your admin panel. Connect GitHub repositories, browse and edit files, and keep CMS content synced with version control without leaving Filament. Built for TomatoPHP Filament CMS workflows.
Github integration to import your repo docs README files as a docs on markdown format to TomatoPHP CMS
Frequently asked questions about Filament Cms Github
- What does tomatophp/filament-cms-github do?
- It is a Filament admin-panel integration that imports GitHub repository docs and README files as Markdown docs into TomatoPHP CMS. It lets you connect repositories, browse and edit files, and keep CMS content synced with version control from the Filament panel. It is built for TomatoPHP Filament CMS workflows and layers onto filament-cms rather than replacing it.
- What are the Laravel, PHP, and Filament version requirements for filament-cms-github?
- The plugin requires Filament v5, Laravel 12 or 13, PHP 8.2 or higher, and tomatophp/filament-cms ^5.0. These are Composer peer locks, so installation will fail if the host app is not already on that track. Confirm the target app's Laravel and Filament versions before adopting it.
- How do I install tomatophp/filament-cms-github in a Laravel app?
- Install it with Composer alongside tomatophp/filament-cms ^5.0 in an app already running Filament v5 and Laravel 12 or 13. The release adds a tested install command, which improves first-run confidence, but you should still review published assets and panel registration. Audit the host app's PHP, Laravel, and Filament versions first because Composer enforces the peer constraints.
- How do I enable the GitHub content import action in Filament?
- The README documents an allowContentImport() gate that must be enabled to surface the GitHub import action. Use that gate to control whether editors can write external repository content into the CMS. Review the import as a write path before enabling it in production.
- Does filament-cms-github work with Filament v3 or v4?
- No. The plugin requires Filament v5, so it is a poor fit for admin panels on Filament v3 or v4 unless you migrate the panel framework first. Do not adopt the plugin as a reason to change Filament versions without a separate panel upgrade decision. If you are on v3 or v4, bundle the Filament v5 upgrade with plugin adoption in one change window.
- Is PHP 8.2 supported by filament-cms-github?
- PHP 8.2 is claimed as the floor, but the CI matrix covers only PHP 8.3 and 8.4, so treat 8.2 as unverified. Standardize on PHP 8.3 for production until 8.2 test coverage is confirmed. Ask the maintainer whether any 8.2 regressions are known.
- Does filament-cms-github support Laravel 13?
- Laravel 13 appears in the version matrix, but it may be pre-release, so adopting the plugin only for Laravel 13 support risks chasing churn. Confirm whether 13 support is GA before relying on it. If you are on Laravel 12, that is the safer supported path in the stated matrix.
- What breaking changes are in filament-cms-github 5.0.0?
- Version 5.0.0 is a coordinated major jump with Filament v5 and two Laravel majors, but the release notes do not include a breaking-change inventory. Renamed config keys, published asset paths, namespace moves, and schema or table changes are all unenumerated. Audit these areas and prepare a restore-from-backup rollback because a documented data-migration path is not described.
- Does filament-cms-github own its own content tables or use filament-cms tables?
- The plugin layers CMS capabilities onto an existing panel and depends on tomatophp/filament-cms ^5.0, which owns the CMS layer. The notes do not clearly state whether the plugin owns content tables or layers on filament-cms tables, so confirm migration and rollback responsibility during evaluation. Treat schema ownership as an audit item before production adoption.
- Is the GitHub import queued or synchronous, and how are credentials handled?
- The provided notes do not specify whether the GitHub import runs queued or synchronously, what credentials it requires, where they are stored, or how rate limits and provenance are handled. Because allowContentImport() gates a write path that imports external content into the CMS, review these production concerns before enabling it. Ask the maintainer for credential scoping, rate-limit behavior, and import execution details.
Weaver
How can I help you explore Laravel packages today?