Jonathan Miller
5cbd0b64d4
Joomla: Extension CI / Tests (PHP 8.2) (pull_request) Blocked by required conditions
Joomla: Extension CI / Tests (PHP 8.3) (pull_request) Blocked by required conditions
Joomla: Extension CI / PHPStan Analysis (pull_request) Blocked by required conditions
Universal: PR Check / Branch Policy (pull_request) Successful in 2s
Joomla: Extension CI / Release Readiness Check (pull_request) Failing after 5s
Universal: Auto Version Bump / Version Bump (push) Failing after 5s
Universal: Secret Scanning / Gitleaks Secret Scan (pull_request) Successful in 5s
Universal: PR Check / Validate PR (pull_request) Successful in 6s
Joomla: Extension CI / Lint & Validate (pull_request) Failing after 7s
Changes: - Delete cascade-dev.yml (disabled; auto-release Step 11 handles dev recreation) - Delete update-server.yml (merged into pre-release.yml) - Consolidate pre-release.yml: now handles push triggers on dev/alpha/beta/rc branches, PR merged to dev, manual dispatch, SFTP deploy, and updates.xml sync - Remove pre-release RC trigger from pr-check.yml (auto-release.yml handles RC via promote-rc job on PR opened to main) - Restrict repo-health.yml to manual dispatch only (was noisy on every push/PR) Workflow count: 12 → 10 Before: pre-release.yml — PR merged to dev + manual update-server.yml — push to dev + PR merged to dev + manual + SFTP deploy pr-check.yml — branch policy + validate + trigger pre-release RC cascade-dev.yml — disabled repo-health.yml — push + PR + manual After: pre-release.yml — push to dev + PR merged to dev + manual + SFTP deploy pr-check.yml — branch policy + validate (no RC trigger) repo-health.yml — manual only Authored-by: Moko Consulting Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Code of Conduct
Our Pledge
We pledge to make participation in our project a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
Our Standards
Examples of behavior that contributes to a positive environment:
- Using welcoming and inclusive language
- Being respectful of differing viewpoints and experiences
- Gracefully accepting constructive criticism
- Focusing on what is best for the community
Examples of unacceptable behavior:
- Trolling, insulting/derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information without explicit permission
Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the project team at hello@mokoconsulting.tech. All complaints will be reviewed and investigated.
Attribution
This Code of Conduct is adapted from the Contributor Covenant, version 2.1.