Template
jmiller
8c579a2841
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Has been skipped
Generic: Project CI / Lint & Validate (pull_request) Has been cancelled
Universal: PR Check / Branch Policy (pull_request) Has been cancelled
Universal: PR Check / Secret Scan (pull_request) Has been cancelled
Universal: PR Check / Validate PR (pull_request) Has been cancelled
Joomla: Metadata Validation / Validate Joomla Metadata (pull_request) Has been cancelled
Generic: Repo Health / Access control (pull_request) Has been cancelled
Generic: Repo Health / Site Health (pull_request) Has been cancelled
Branch Cleanup / Delete merged branch (pull_request) Has been cancelled
RC Revert / Rename rc/ back to dev/ (pull_request) Has been cancelled
Universal: Workflow Sync Trigger / Sync workflows to live repos (pull_request) Has been cancelled
Generic: Project CI / Tests (pull_request) Has been cancelled
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Generic: Repo Health / Scripts governance (pull_request) Has been cancelled
Generic: Repo Health / Repository health (pull_request) Has been cancelled
Generic: Repo Health / Report: Scripts Governance (pull_request) Has been cancelled
Generic: Repo Health / Report: Repository Health (pull_request) Has been cancelled
Rework the SQL-schema check so each component is validated against ITS OWN manifest version instead of a single package-level version applied to every sql/updates/mysql dir (which mis-flagged independently-versioned sub-extensions). Add check #11: fail if any update file version exceeds its component manifest version. This catches migration files drifting onto a different numbering lane and getting ahead of the release version (e.g. 01.14.00.sql while the manifest is 01.01.40) at PR time instead of surfacing as a runtime schema mismatch. Authored-by: Moko Consulting Claude-Session: https://claude.ai/code/session_01VXrBk7psPzJPHVuBDJwt2x
Contributor Covenant Code of Conduct
Our Pledge
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone.
Our Standards
- Be empathetic and kind
- Be respectful of differing opinions
- Accept constructive feedback
- Own mistakes and learn from them
Unacceptable behavior includes sexualized language/imagery, trolling, harassment, doxing, and other inappropriate conduct.
Enforcement
Report incidents to hello@mokoconsulting.tech or through GitHub Discussions if you prefer a community-visible approach. Private complaints will be reviewed promptly and fairly.
Enforcement Guidelines
- Correction — Private warning
- Warning — Formal warning and limited interaction
- Temporary Ban — Time-boxed exclusion
- Permanent Ban — Removal from the community
Attribution
Adapted from the Contributor Covenant v2.1.