Download the PHP package liberusoftware/boilerplate-scripts without Composer
On this page you can find all versions of the php package liberusoftware/boilerplate-scripts. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download liberusoftware/boilerplate-scripts
More information about liberusoftware/boilerplate-scripts
Files in liberusoftware/boilerplate-scripts
Package boilerplate-scripts
Short Description Release, repository splitting, and Packagist publishing automation for Liberu Composer packages.
License MIT
Informations about the package boilerplate-scripts
Liberu Meta Repository Scripts
Generic release and maintenance automation for Composer-based meta repositories whose modules, themes, and shared tooling live in independent GitHub repositories.
Copy .liberu-meta.json from a meta repository and customize its organization,
genre, repository, component paths, prefixes, and additional Composer packages.
setup.shperforms a repeatable local or production install without destructive migrations.update.shupdates dependencies and validates the project;--release 1.2.3commits, tags, pushes, and creates a GitHub release after successful checks.submit-packagist.phpcreates missing Packagist packages and refreshes existing package metadata.fleetfans a command across the component repositories once they are the source of truth —status,clone,run,commit, and a separatetagthat only ever acts on an explicit--onlylist. It replacedpublish-components, which rsynced a monorepo into its component repositories — the opposite direction, and meaningless once those repositories are the source.set-coverage-thresholdswrites each measured figure into that package'stests.yml, ratcheting only upward — a package that has lost coverage keeps its threshold and is reported.measure-coverageresolves each package from nothing and runs its own suite under pcov, writingstorage/app/coverage.tsv— the evidence a repository sets its coverage threshold from.
All commands are non-interactive and fail on errors. GitHub operations require an
authenticated gh CLI. Packagist operations read PACKAGIST_USERNAME and
PACKAGIST_API_TOKEN from the environment; never commit either credential.