Step 15 — Contribute to PioniaCore

You built an app on Packagist; some teams fix bugs or add features in the framework itself.

What you will learn#

• Clone PioniaCore and run the test suite
• Scaffold apps from the monorepo for framework work
• Where docs, AGENTS.md, and release tooling live

Clone and test#

git clone https://github.com/PioniaPHP-project/PioniaCore.git
cd PioniaCore
composer install
bin/test

Every framework change needs tests on PHP 8.5+. Read AGENTS.md in the repo root before editing src/Pionia/.

Local app from monorepo#

Framework maintainers scaffold with the example CLI (not composer create-project):

php example/pionia new my-fix-app --install

Use this when you need to reproduce a bug against your local pionia/pionia-core checkout.

Contribute docs#

This tutorial lives in pionia-docs. Fix typos or add steps via PR — follow content/docs/DOCUMENTATION_STYLE.md.

Contribute code#

Full maintainer reference: Maintainer notes.

You finished DeskFlow#

Step 1  → project on disk
Step 7  → SQLite CRUD
Step 9  → authenticated writes
Step 13 → production workers
Step 14 → provider hooks
Step 15 → framework contribution path

Common mistakes#

• Using pionia new as an app developer — Packagist pionia/pionia-app is the supported app path; monorepo scaffolds are for core contributors.
• PRs without tests — CI enforces coverage on src/Pionia/.

What’s next#