Weave Code
Ghygen Laravel Package
hi-folks/ghygen
Ghygen generates GitHub Actions workflow YAML for Laravel projects via an intuitive GUI, handling PHP matrix testing, caching, database services, and deployment steps. Skip hand-writing CI config and get a ready-to-use pipeline in minutes.
Ghygen is a GitHub Actions workflow generator for Laravel and PHP projects. It turns common CI choices—PHP and Laravel versions, triggers, services, and test commands—into a ready-to-commit YAML workflow, reducing boilerplate and configuration mistakes.
- Interactive workflow builder for PHP/Laravel matrices
- Configurable triggers, branches, schedules, and manual runs
- Optional MySQL, PostgreSQL, Redis, and cache services
- Steps for tests, static analysis, and code style checks
- Generates clean
.github/workflowsfiles ready for review
Frequently asked questions about Ghygen
- What is Ghygen and how does it help Laravel developers?
- Ghygen is a GitHub Actions configurator for PHP and Laravel projects. It provides a web interface and CLI that generate ready-to-use workflow YAML for tests, static analysis, and deployment. It is a developer productivity tool that produces a configuration artifact, not a runtime library. The committed YAML is what your team owns and operates.
- Do I install Ghygen as a Composer dependency in my Laravel app?
- No, it should not be added to require or require-dev. There is no service provider, API surface, or runtime behavior to integrate with. Use the hosted web UI for zero setup or run the CLI as a global tool or phar. It belongs in your developer tooling bucket, never in the application dependency graph.
- Which Laravel and PHP versions does Ghygen support?
- The tool emits plain GitHub Actions YAML and has no runtime version constraints. Compatibility depends on whether the generated workflow matches your PHP, Laravel, and runner image matrix. The last release was 2024-03-17, so verify support for newer Laravel and PHP versions. Review and adjust generated PHP versions, extensions, and services before committing.
- What is included in the generated GitHub Actions YAML?
- It typically covers steps for installing dependencies, running tests and static analysis, and deployment scaffolding. The output can encode assumptions about PHP versions, extensions, database service containers, and cache paths. Treat it as a candidate workflow and review every line against your repo's actual matrix. It is not guaranteed to match your project without hand-editing.
- Can Ghygen generate matrix builds and MySQL or Redis service containers?
- The generator is designed to produce PHP and Laravel CI workflows including common service containers and matrix strategies, but exact options depend on the UI or CLI version and templates. Because the last release is from March 2024, confirm the generated syntax matches current GitHub Actions features. Always test on a throwaway branch and add anything missing by hand.
- Is it safe to run Ghygen against my repository?
- It generates YAML based on inputs or repo metadata, and nothing ships to production, so application risk is negligible. CI reliability risk is moderate because unreviewed output can create green-but-hollow or red-but-fixable pipelines. Prefer the web UI with no install or run the CLI in a throwaway container. Review the output for secrets handling and third-party actions before committing.
- How actively is Ghygen maintained?
- Community signals are modest: around 332 GitHub stars, zero dependents, and a last release dated 2024-03-17. The repository description is also stale or mismatched, which is a metadata hygiene flag. Treat it as a single-maintainer tool with a low bus factor. Plan to own the generated YAML regardless of upstream activity.
- Should I use Ghygen or a reusable workflow template?
- Ghygen is strongest at bootstrap, producing a candidate workflow quickly. Once hardened, extract it into an internal reusable workflow using workflow_call or an org template. That way the generator is a one-time reference rather than an ongoing crutch. If hand-editing is heavy, a curated template may be the better long-term choice.
- How do I test a Ghygen-generated workflow safely?
- Generate the YAML, review it line by line against your test matrix, extensions, and services, then commit it to a non-critical branch. Run the workflow there and measure how much hand-editing is required. Only move it to default-branch CI after it passes. Keep the committed YAML versioned and diff future generations against that baseline.
- Does Ghygen work for private repositories or require repo access?
- The web UI is a configurator that produces YAML, so you copy the output into your repo and it does not need ongoing access. The CLI runs locally or in a container against your project. Either way, review what metadata the tool reads and avoid pasting secrets into third-party interfaces. The durable artifact is the YAML you commit.
Weaver
How can I help you explore Laravel packages today?