LaravelPackages.net
Acme Inc.
Toggle sidebar
bradleyrmartin/laravel-init

A Laravel scaffolding package that publishes opinionated starter files into your application.

3
0
1.0.4
About bradleyrmartin/laravel-init

bradleyrmartin/laravel-init is a Laravel package for a laravel scaffolding package that publishes opinionated starter files into your application.. It currently has 0 GitHub stars and 3 downloads on Packagist (latest version 1.0.4). Install it with composer require bradleyrmartin/laravel-init. Discover more Laravel packages by bradleyrmartin or browse all Laravel packages to compare alternatives.

Last updated

bradleyrmartin/laravel-init

A Laravel scaffolding package that publishes opinionated starter files into your application.

Requires: Laravel 13+ · PHP 8.3+


Installation

composer require bradleyrmartin/laravel-init

The service provider is auto-discovered by Laravel.


Publishing Assets

Publish all assets at once:

php artisan laravel-init:publish

Or publish a specific group:

| Tag | What it publishes | |-----|-------------------| | laravel-init | Everything | | laravel-init-controllers | app/Http/Controllers/Controller.php | | laravel-init-cursor | .cursor/rules/ Cursor AI rules |

# Publish controllers only
php artisan laravel-init:publish --tag=laravel-init-controllers

# Publish Cursor rules only
php artisan laravel-init:publish --tag=laravel-init-cursor

# Force overwrite existing files
php artisan laravel-init:publish --force

You can also use the standard Laravel vendor:publish command directly:

php artisan vendor:publish --provider="BradleyRMartin\LaravelInit\LaravelInitServiceProvider" --tag=laravel-init

Published Files

app/
└── Http/
    └── Controllers/
        └── Controller.php

.cursor/
└── rules/
    └── laravel.mdc

Development

Branches

| Branch | Purpose | |--------|---------| | main | Stable, Packagist-published code | | next | Active development — all PRs target this branch |

Workflow

  1. Create a feature branch off next
  2. Open a PR targeting next — tests run automatically
  3. Merge the PR into next
  4. When ready to release, create a GitHub Release with a semver tag (e.g. v1.2.0)
  5. The release workflow will automatically:
    • Bump package.json to the release version
    • Commit the bump to next
    • Merge next into main
    • Notify Packagist to pull the latest main

Required GitHub Secrets

| Secret | Description | |--------|-------------| | RELEASE_TOKEN | A GitHub Personal Access Token with repo scope (needed to push and merge branches) | | PACKAGIST_TOKEN | Your Packagist API token (username bradleyrmartin is hardcoded in the workflow) |

Running Tests Locally

composer install
./vendor/bin/pest

License

MIT

Comments