This guide provides a comprehensive overview of how to use the Core CLI to manage your development workflow.
A Project is a single repository containing code (Go, PHP, or Wails). Core helps you test, build, and release these projects using a consistent set of commands.
A Workspace is a collection of related projects. Core is designed to work across multiple repositories, allowing you to perform actions (like checking status or committing changes) on all of them at once.
The Registry is a configuration file that defines the repositories in your workspace. It includes information about where they are located on GitHub, their dependencies, and their purpose.
For a typical day-to-day development on a single project:
- Verify your environment:
core doctor
- Run tests while you work:
core go test - Keep code clean:
core go fmt --fix core go lint
- Build and preview:
core build
If you are working across many repositories in a workspace:
- Check status of all repos:
core dev work --status
- Sync all changes:
core dev pull --all
- Commit and push everything:
core dev work
Core separates the building of artifacts from the releasing of those artifacts.
The core build command detects your project type and builds binaries for your configured targets. Artifacts are placed in the dist/ directory.
Use core ci to see a summary of what would be included in a release (changelog, artifacts, etc.). This is a dry-run by default.
When you are ready to publish to GitHub:
core ci --we-are-go-for-launchCore provides a unified development server for Laravel projects that orchestrates several services:
core php devThis starts FrankenPHP, Vite, Horizon, Reverb, and Redis as configured in your .core/php.yaml.
For detailed examples of common end-to-end workflows, see the Workflows page.
- Use the
--helpflag with any command:core build --help - Check the FAQ for common questions.
- If you run into trouble, see the Troubleshooting Guide.