MokoConsulting/MokoGitea-APP
1
0
Fork 0
Code Issues 158 Pull Requests 5 Releases 96 Wiki Activity

chore: rename moko-platform to MokoPlatform #548

New Issue
Closed
opened 2026-06-06 23:20:00 +00:00 by jmiller · 0 comments
jmiller commented 2026-06-06 23:20:00 +00:00
Owner
Copy Link
Copy Source

Breaking Change

Rename the moko-platform repository to MokoPlatform to match the CamelCase naming convention used by all other product repos.

Steps

  1. Rename repo on Gitea (API or admin UI)
  2. Update SSH mount path on git.mokoconsulting.tech server
  3. Update all workflow references across all repos (bulk_sync, standards-source URLs)
  4. Update manifest.xml standards-source URLs
  5. Update local clone paths (A:/moko-platform -> A:/MokoPlatform)
  6. Update .claude.json MCP server paths
  7. Update npm package.json repository URLs
  8. Update Go module imports in MokoGitea (code.mokoconsulting.tech/MokoConsulting/moko-platform)

Risk

  • All repos reference moko-platform in workflows and manifests
  • SSH mount on server needs updating
  • Local development paths change
  • CI/CD pipelines may break temporarily

Authored by Jonathan Miller (@jmiller)

## Breaking Change Rename the moko-platform repository to MokoPlatform to match the CamelCase naming convention used by all other product repos. ## Steps 1. Rename repo on Gitea (API or admin UI) 2. Update SSH mount path on git.mokoconsulting.tech server 3. Update all workflow references across all repos (bulk_sync, standards-source URLs) 4. Update manifest.xml standards-source URLs 5. Update local clone paths (A:/moko-platform -> A:/MokoPlatform) 6. Update .claude.json MCP server paths 7. Update npm package.json repository URLs 8. Update Go module imports in MokoGitea (code.mokoconsulting.tech/MokoConsulting/moko-platform) ## Risk - All repos reference moko-platform in workflows and manifests - SSH mount on server needs updating - Local development paths change - CI/CD pipelines may break temporarily --- *Authored by Jonathan Miller (@jmiller)*
Sign in to join this conversation.
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 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
 sync-failure
Sync or mirror failed
 tech-debt
Technical debt and TODO/FIXME items
 upstream
upstream
Inherited from upstream Gitea
 work-in-progress
Draft or incomplete work
No labels
Priority -
Type -
Status —
Priority —
Type —
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller) moko-deploy (Moko Deploy Bot)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGitea-APP#548
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?