MokoConsulting/mokoplatform
1
0
Fork 0
Code Issues 9 Pull Requests Releases 8 Wiki Activity

docs: update moko-platform wiki with CLI tool reference #66

New Issue
Closed
opened 2026-05-23 22:57:55 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-23 22:57:55 +00:00
Owner
Copy Link
Copy Source

Summary

Create or update wiki pages documenting all CLI tools in moko-platform.

Wiki pages needed

  • CLI Reference - index of all CLI tools with usage examples
  • Release Pipeline - how auto-release.yml uses CLI tools, step-by-step
  • Platform Detection - how manifest.xml drives platform-specific behavior

Depends on

All CLI extraction issues being completed.

Notes

Wiki is the preferred documentation location (not docs/ in repo). Each CLI tool should have its own section with:

  • Purpose
  • Arguments (--flags)
  • Output format
  • Example usage in workflows
## Summary Create or update wiki pages documenting all CLI tools in moko-platform. ## Wiki pages needed - **CLI Reference** - index of all CLI tools with usage examples - **Release Pipeline** - how auto-release.yml uses CLI tools, step-by-step - **Platform Detection** - how manifest.xml drives platform-specific behavior ## Depends on All CLI extraction issues being completed. ## Notes Wiki is the preferred documentation location (not docs/ in repo). Each CLI tool should have its own section with: - Purpose - Arguments (--flags) - Output format - Example usage in workflows
jmiller commented 2026-05-24 03:40:39 +00:00
Author
Owner
Copy Link
Copy Source

CLI tools implemented on feature/cli-release-tools. This issue remains open to track wiki documentation after merge.

CLI tools to document:

Tool Purpose
release_verify.php Post-release artifact verification
release_validate.php Pre-release sanity checks
release_body_update.php Update release body with changelog + SHA
dev_branch_reset.php Delete/recreate dev branch via API
updates_xml_build.php Generate updates.xml from manifest
package_build.php Build ZIP/tar.gz with checksums
release_cascade.php Delete lesser pre-release channels
platform_detect.php Detect platform from manifest.xml
version_bump.php Bump version in README.md
changelog_promote.php Promote [Unreleased] in CHANGELOG.md
version_set_platform.php Set version across platform manifests
CLI tools implemented on `feature/cli-release-tools`. This issue remains open to track wiki documentation after merge. ### CLI tools to document: | Tool | Purpose | |---|---| | release_verify.php | Post-release artifact verification | | release_validate.php | Pre-release sanity checks | | release_body_update.php | Update release body with changelog + SHA | | dev_branch_reset.php | Delete/recreate dev branch via API | | updates_xml_build.php | Generate updates.xml from manifest | | package_build.php | Build ZIP/tar.gz with checksums | | release_cascade.php | Delete lesser pre-release channels | | platform_detect.php | Detect platform from manifest.xml | | version_bump.php | Bump version in README.md | | changelog_promote.php | Promote [Unreleased] in CHANGELOG.md | | version_set_platform.php | Set version across platform manifests |
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 Low
Type Documentation
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/mokoplatform#66
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?