MokoConsulting/MokoJoomOpenGraph
1
0
Fork 0
Code Issues 12 Pull Requests 1 Releases 3 Wiki Activity

chore: cascade main → dev (1b09c5d) [skip ci] #28

Merged
jmiller merged 7 commits from main into dev 2026-05-24 03:44:24 +00:00
Conversation 0 Commits 7 Files Changed 3
+112 -142
jmiller commented 2026-05-24 03:44:22 +00:00
Owner
Copy Link
Copy Source

Automatic cascade

Forward-merging main (1b09c5d) into dev.

If conflicts exist, resolve manually and merge.

Auto-created by Cascade Main → Dev.

## Automatic cascade Forward-merging `main` (1b09c5d) into `dev`. If conflicts exist, resolve manually and merge. > Auto-created by **Cascade Main → Dev**.
jmiller added 7 commits 2026-05-24 03:44:22 +00:00
chore: update .mokogitea/manifest.xml with standard format
Universal: Cascade Main → Dev / Cascade main → branches (push) Successful in 2s
Details
8feb75e1c7 
Add Moko Platform header comment, last-synced timestamp, and
normalize indentation to match other repos.

Authored-by: Moko Consulting

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
chore: sync updates.xml from [skip ci] 02692440ba
chore: sync updates.xml from [skip ci] bb064a4c20
chore: sync updates.xml from [skip ci] 5a99987e0f
chore: sync updates.xml from [skip ci] 84705d92f6
chore: sync updates.xml from [skip ci] 59536181da
chore: remove deploy workflow — switching to Joomla update server method
Joomla: Repo Health / Access control (push) Successful in 1s
Details
Universal: Cascade Main → Dev / Cascade main → branches (push) Successful in 5s
Details
Joomla: Repo Health / Release configuration (push) Has been cancelled
Details
Joomla: Repo Health / Scripts governance (push) Has been cancelled
Details
Joomla: Repo Health / Repository health (push) Has been cancelled
Details
1b09c5d10c
jmiller merged commit f9b4ca880c into dev 2026-05-24 03:44:24 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is broken
 documentation
Documentation improvements
 enhancement
priority: high
priority: low
priority: medium
production-readiness
Required before v1.0 release
 security
Security vulnerability or hardening
 testing
Test coverage and QA
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
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoJoomOpenGraph#28
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?