Skip to content

OPS Workflow

OPS work is operational server or environment work. It does not require a PR unless repository code changes.

OPS Examples

  • OpenCart installation.
  • Nginx or Apache configuration.
  • PHP-FPM configuration.
  • Database setup.
  • SSL configuration.
  • Permissions and storage paths.
  • Cron setup.
  • Composer or npm install on the server.
  • Vhosts and document roots.

Issue Format

Create or update a GitHub issue with a title like:

OPS: short description

The issue or comment should include:

  • what was done;
  • paths and document roots;
  • domains;
  • versions;
  • PHP version;
  • database status;
  • storage paths;
  • web server notes;
  • permissions;
  • validation;
  • known issues;
  • reference links when used.

PR Boundary

Do not open a PR for server state alone. If repository files change, use the normal branch and PR workflow.

Review Boundary

ChatGPT can review OPS issues and PRs separately. OPS issues describe environment state; repository docs describe product and architecture decisions.