MokoConsulting/mokocli
Public Access
1
0
Fork 0
Code Issues 9 Pull Requests 1 Releases 8 Wiki Activity

Rename "mokoplatform" to "MokoCLI" everywhere #262

New Issue
Closed
opened 2026-06-19 09:05:46 +00:00 by jmiller · 1 comment
jmiller commented 2026-06-19 09:05:46 +00:00
Owner
Copy Link
Copy Source

Summary

Rename all references from mokoplatform to MokoCLI across the entire project.

Sub-tasks

# Task Status
#276 Add redirect stubs and backward-compatibility aliases (do first) Open
#263 Update composer.json, package.json, and config files Open
#264 Update PHP namespaces, classes, and code references Open
#265 Update CLI command names, help text, and output messages Open
#266 Update CI/CD workflows and Gitea Actions Open
#267 Update runner labels and runner configuration Open
#268 Update documentation (README, wiki, CHANGELOG) Open
#269 Update MCP server configs and references Open
#270 Rename the Git repository and update external references (do last) Open

Casing Convention

  • MokoCLI — display / branding
  • mokocli — package names, filesystem paths, repo name

Suggested Order

  1. Redirect stubs (#276) — first, set up aliases so nothing breaks during transition
  2. Config files (#263) + PHP code (#264) — foundation changes
  3. CLI text (#265) — user-facing updates
  4. CI/CD (#266) + Runners (#267) — infrastructure (coordinate together)
  5. MCP configs (#269) — service layer
  6. Documentation (#268) — reflect all changes
  7. Repo rename (#270) — last step, after everything else is merged
## Summary Rename all references from `mokoplatform` to `MokoCLI` across the entire project. ## Sub-tasks | # | Task | Status | |---|------|--------| | #276 | Add redirect stubs and backward-compatibility aliases (**do first**) | Open | | #263 | Update composer.json, package.json, and config files | Open | | #264 | Update PHP namespaces, classes, and code references | Open | | #265 | Update CLI command names, help text, and output messages | Open | | #266 | Update CI/CD workflows and Gitea Actions | Open | | #267 | Update runner labels and runner configuration | Open | | #268 | Update documentation (README, wiki, CHANGELOG) | Open | | #269 | Update MCP server configs and references | Open | | #270 | Rename the Git repository and update external references (**do last**) | Open | ## Casing Convention - `MokoCLI` — display / branding - `mokocli` — package names, filesystem paths, repo name ## Suggested Order 1. Redirect stubs (#276) — **first**, set up aliases so nothing breaks during transition 2. Config files (#263) + PHP code (#264) — foundation changes 3. CLI text (#265) — user-facing updates 4. CI/CD (#266) + Runners (#267) — infrastructure (coordinate together) 5. MCP configs (#269) — service layer 6. Documentation (#268) — reflect all changes 7. Repo rename (#270) — **last step**, after everything else is merged
jmiller commented 2026-06-19 09:05:49 +00:00
Author
Owner
Copy Link
Copy Source

Branch created: feature/262-rename-mokoplatform-to-mokocli-everywher

git fetch origin
git checkout feature/262-rename-mokoplatform-to-mokocli-everywher
Branch created: [`feature/262-rename-mokoplatform-to-mokocli-everywher`](https://git.mokoconsulting.tech/MokoConsulting/mokoplatform/src/branch/feature/262-rename-mokoplatform-to-mokocli-everywher) ```bash git fetch origin git checkout feature/262-rename-mokoplatform-to-mokocli-everywher ```
Sign in to join this conversation.
Labels
Clear labels
automation
Automated processes or scripts
 breaking-change
Breaking API or functionality change
 build
Build system changes
 ci-cd
CI/CD pipeline changes
 config
Configuration file changes
 css
CSS/styling changes
 dependencies
Dependency updates
 deploy-failure
Automated deploy failure tracking
 docker
Docker configuration changes
 documentation
Documentation changes
 dolibarr
Dolibarr module or extension
 generic
Generic project or library
 good first issue
Good for newcomers
 health-check
Repository health check results
 health: excellent
Health score 90-100
 health: fair
Health score 50-69
 health: good
Health score 70-89
 health: poor
Health score below 50
 help wanted
Extra attention needed
 html
HTML template changes
 javascript
JavaScript code changes
 joomla
Joomla extension or component
 mokostandards
MokoStandards compliance
 needs-review
Awaiting code review
 php
PHP code changes
 push-failure
File push failure requiring attention
 python
Python code changes
 security
Security-related changes
 size/l
Large change (101-300 lines)
 size/m
Medium change (31-100 lines)
 size/s
Small change (11-30 lines)
 size/xl
Extra large change (301-1000 lines)
 size/xs
Extra small change (1-10 lines)
 size/xxl
Extremely large change (1000+ lines)
 standards-drift
Repository drifted from MokoStandards
 standards-update
MokoStandards sync update
 sync-failure
Bulk sync failure requiring attention
 sync-report
Bulk sync run report
 template-validation-failure
Template workflow validation failure
 tests
Test suite changes
 type: bug
Something isn't working
 type: chore
Maintenance tasks
 type: enhancement
Enhancement to existing feature
 type: feature
New feature or request
 type: refactor
Code refactoring
 type: version
Version-related change
 typescript
TypeScript code changes
 version
Version bump or release
 version-drift
Version mismatch detected
 work-in-progress
Work in progress, not ready for merge
No labels
Priority Medium
Type Feature
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/mokocli#262
Delete Branch "%!s()"

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?