MokoConsulting/Template-Joomla
Template
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore: cascade main → dev (6544b6d) [skip ci] #4

Merged
jmiller merged 6 commits from main into dev 2026-05-12 04:01:46 +00:00
Conversation 0 Commits 6 Files Changed 15
+194 -221
jmiller commented 2026-05-12 04:01:45 +00:00
Owner
Copy Link
Copy Source

Automatic cascade

Forward-merging main (6544b6d) into dev.

If conflicts exist, resolve manually and merge.

Auto-created by Cascade Main → Dev.

## Automatic cascade Forward-merging `main` (6544b6d) into `dev`. If conflicts exist, resolve manually and merge. > Auto-created by **Cascade Main → Dev**.
jmiller added 6 commits 2026-05-12 04:01:45 +00:00
chore: sync auto-release.yml from MokoGalleryCalendar [skip ci] 5dcbddb9e2
Merge branch 'dev'
Joomla: Repo Health / Access control (push) Successful in 1s
Details
Universal: Cascade Main → Dev / Cascade main → branches (push) Successful in 1s
Details
Joomla: Repo Health / Release configuration (push) Failing after 3s
Details
Joomla: Repo Health / Scripts governance (push) Successful in 3s
Details
Joomla: Repo Health / Repository health (push) Failing after 2s
Details
5c209b1671 
# Conflicts:
#	.gitea/workflows/auto-release.yml
chore: move workflows to .mokogitea/workflows/ [skip ci] b5003ebd48
chore: move all workflows to .mokogitea/workflows/ [skip ci] e0b96594b7
chore: remove .gitea/ and .github/ directories [skip ci] fc8f039741
feat(workflows): merge branch policy into pr-check.yml
Joomla: Repo Health / Access control (push) Successful in 1s
Details
Universal: Cascade Main → Dev / Cascade main → branches (push) Successful in 2s
Details
Joomla: Repo Health / Release configuration (push) Failing after 2s
Details
Joomla: Repo Health / Scripts governance (push) Successful in 2s
Details
Joomla: Repo Health / Repository health (push) Failing after 3s
Details
6544b6dae7 
- Combine pr-branch-check.yml into pr-check.yml as a separate job
- Add platform-aware validation (joomla/dolibarr/generic)
- Delete standalone pr-branch-check.yml

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
jmiller merged commit cbcaed660b into dev 2026-05-12 04:01:46 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 html
HTML/template changes
 joomla
Joomla extension
 major-release
Major version release
 minor-release
Minor version release
 mokostandards
Related to MokoStandards framework
 patch-release
Patch version release
 php
PHP code
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 push-failure
Git push operation failed
 release-candidate
Release candidate build
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 type: bug
Something isn't working
 type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 version-drift
Version mismatch across files
 work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 pending: dependency
Blocked by another issue or external dependency
 pending: deployment
Tested and approved, awaiting deployment to production
 pending: design
Needs UI/UX or architecture design before implementation
 pending: documentation
Feature works, needs documentation/wiki update
 pending: feedback
Awaiting feedback or decision from stakeholder
 pending: review
Implementation complete, awaiting code review
 pending: testing
Feature implemented but not yet tested
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/Template-Joomla#4
Delete Branch "main"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?