$ composer test

Contribute to OC-CLI

The best contributions are repo-aligned, well-tested, and explicit about behavioral changes. The commands below mirror the current `oc-cli` repository.

Ways to Help

Command work

Add focused features, tighten validation, or improve runtime and database behaviors while preserving the documented command surface.

Documentation

Keep usage examples, installation guidance, and capability boundaries aligned with the actual repository.

Verification

Add or improve unit, integration, and end-to-end coverage when behavior changes or new commands are introduced.

Issue triage

Reproduce bugs, narrow failing scenarios, and contribute actionable issue reports or fixes.

Local Setup

Clone your fork

Terminal
git clone https://github.com/YOUR-USERNAME/oc-cli.git

Enter the repository

Terminal
cd oc-cli

Install dependencies

Terminal
composer install

Required Checks

Before opening a pull request, run the checks the current repository documents for day-to-day verification. 

composer test
composer cs-check
composer analyze

For changes that affect installer behavior, binary behavior, or the OpenCart runtime harness, also consider the repo's end-to-end flow via `composer test:e2e`.

Contribution Guidelines

  • Keep new behavior explicit. If a command only supports OpenCart 3.x runtime bootstrap today, document that constraint instead of softening it.
  • Update tests and docs together when command syntax or output changes.
  • Prefer focused pull requests over broad refactors that mix unrelated concerns.
  • Match the repo's current naming and command style. The package binary is `oc`.

Repository links

Use GitHub issues for bugs, discussions for broader ideas, and pull requests for concrete changes.

Repository Issues Discussions