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

fix: rename moko-platform to MokoCLI in documentation (#268)
Generic: Repo Health / Scripts governance (push) Blocked by required conditions
Details
Generic: Repo Health / Repository health (push) Blocked by required conditions
Details
Generic: Repo Health / Report Issues (push) Blocked by required conditions
Details
Generic: Repo Health / Site Health (push) Has been skipped
Details
Generic: Repo Health / Access control (push) Successful in 2s
Details
Platform: MokoCLI CI / Gate 2: Unit Tests (8.1) (pull_request) Blocked by required conditions
Details
Platform: MokoCLI CI / Gate 2: Unit Tests (8.2) (pull_request) Blocked by required conditions
Details
Platform: MokoCLI CI / Gate 2: Unit Tests (8.3) (pull_request) Blocked by required conditions
Details
Platform: MokoCLI CI / Gate 3: Self-Health Check (pull_request) Blocked by required conditions
Details
Platform: MokoCLI CI / Gate 4: Governance (pull_request) Blocked by required conditions
Details
Platform: MokoCLI CI / Gate 5: Template Integrity (pull_request) Blocked by required conditions
Details
Platform: MokoCLI CI / CI Summary (pull_request) Blocked by required conditions
Details
Universal: PR Check / Build RC Package (pull_request) Blocked by required conditions
Details
Universal: PR Check / Report Issues (pull_request) Blocked by required conditions
Details
Generic: Repo Health / Scripts governance (pull_request) Blocked by required conditions
Details
Generic: Repo Health / Repository health (pull_request) Blocked by required conditions
Details
Generic: Repo Health / Report Issues (pull_request) Blocked by required conditions
Details
Universal: PR Check / Branch Policy (pull_request) Successful in 4s
Details
Universal: PR Check / Validate PR (pull_request) Successful in 8s
Details
Generic: Repo Health / Access control (pull_request) Successful in 2s
Details
Generic: Repo Health / Site Health (pull_request) Has been skipped
Details
Platform: MokoCLI CI / Gate 1: Code Quality (pull_request) Failing after 1m31s
Details
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Failing after 5s
Details

Browse Source 
Update all markdown files: README, CHANGELOG, CLAUDE.md, index files,
templates, issue templates, and inline documentation.
This commit is contained in:
Jonathan Miller
2026-06-20 11:39:54 -05:00
parent 1274e2866b
commit a5a16fb7e3
49 changed files with 360 additions and 360 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.mokogitea/CLAUDE.md
+3 -3
View File
@@ -1,4 +1,4 @@
# moko-platform
# MokoCLI
Enterprise automation, validation, sync, and governance engine for all Moko Consulting repositories.
@@ -9,7 +9,7 @@ Enterprise automation, validation, sync, and governance engine for all Moko Cons
| **Language** | PHP 8.1+ |
| **Version** | 09.01.00 |
| **Branch** | develop on `dev`, merge to `main` (protected) |
| **Wiki** | [moko-platform Wiki](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/wiki) |
| **Wiki** | [MokoCLI Wiki](https://git.mokoconsulting.tech/MokoConsulting/mokocli/wiki) |
## Commands
@@ -73,4 +73,4 @@ PHPStan runs with `--memory-limit=512M`. CI enforces PHPCS errors; PHPStan is `c
- **Workflow directory**: `.mokogitea/` (not `.gitea/` or `.github/`)
- **Wiki**: documentation lives in the Gitea wiki, not `docs/` files
- **New CLI tools**: extend `CliFramework`, not `CLIApp` (legacy)
- **Standards**: [MokoStandards](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/wiki/Home)
- **Standards**: [MokoStandards](https://git.mokoconsulting.tech/MokoConsulting/mokocli/wiki/Home)
.mokogitea/ISSUE_TEMPLATE/documentation.md
+1 -1
View File
@@ -42,7 +42,7 @@ Suggested text here
<!-- Add any other context, screenshots, or references -->
## Standards Alignment
- [ ] Follows moko-platform documentation guidelines
- [ ] Follows MokoCLI documentation guidelines
- [ ] Uses en_US/en_GB localization
- [ ] Includes proper SPDX headers where applicable
.mokogitea/ISSUE_TEMPLATE/feature_request.md
+1 -1
View File
@@ -37,7 +37,7 @@ If you have ideas about how this could be implemented, share them here:
Add any other context, mockups, or screenshots about the feature request here.
## Relevant Standards
Does this relate to any standards in [moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)?
Does this relate to any standards in [MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli)?
- [ ] Accessibility (WCAG 2.1 AA)
- [ ] Localization (en_US/en_GB)
- [ ] Security best practices
.mokogitea/ISSUE_TEMPLATE/security.md
+1 -1
View File
@@ -35,7 +35,7 @@ Use this template only for:
<!-- Describe how this could be addressed -->
## Standards Reference
Does this relate to security standards in [moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)?
Does this relate to security standards in [MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli)?
- [ ] SPDX license identifiers
- [ ] Secret management
- [ ] Dependency security
CHANGELOG.md
+1 -1
View File
@@ -4,7 +4,7 @@ SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoStandards.Root
INGROUP: MokoStandards
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /CHANGELOG.md
BRIEF: Release changelog
-->
CONTRIBUTING.md
+161 -161
View File
@@ -1,161 +1,161 @@
# Contributing to Moko Consulting Projects
Thank you for your interest in contributing. All Moko Consulting repositories follow this universal workflow and version policy.
## Branching Workflow
```
feature/* ──PR──> dev ──draft PR──> (renamed to rc) ──merge──> main
```
### Step by step
1. **Create a feature branch** from `dev`:
```bash
git checkout dev && git pull
git checkout -b feature/my-change
```
2. **Work and commit** on your feature branch. Push to origin.
3. **Open a PR**: `feature/my-change` → `dev`. After review and checks, merge it.
4. **When ready for release**, open a **draft PR**: `dev` → `main`.
- This automatically renames the source branch to `rc` (release candidate)
- An RC pre-release is built and uploaded
5. **Alpha and beta branches** are created by manually renaming the branch before the RC stage:
- Rename `dev` to `alpha` for early testing → alpha pre-release is built
- Rename `alpha` to `beta` for feature-complete testing → beta pre-release is built
- When the draft PR is created, the branch is renamed to `rc`
6. **Once PR checks pass** on the `rc` branch, mark the PR as ready and merge to `main`.
7. **Merging to main** triggers the stable release pipeline:
- Minor version bump (e.g., `02.09.xx` → `02.10.00`)
- Stability suffix stripped (clean version)
- Gitea release created with ZIP/tar.gz packages
- `updates.xml` updated (Joomla extensions)
- `dev` branch recreated from `main`
### Branch summary
| Branch | Purpose | Created by |
|--------|---------|-----------|
| `feature/*` | New features and fixes | Developer |
| `dev` | Integration branch | Auto-recreated after release |
| `alpha` | Alpha pre-release testing | Manual rename from `dev` |
| `beta` | Beta pre-release testing | Manual rename from `alpha` |
| `rc` | Release candidate | Auto-renamed on draft PR to main |
| `main` | Stable releases | Protected, merge only |
| `version/XX.YY.ZZ` | Archived release snapshots | Auto-created by CI |
### Protected branches
| Branch | Direct push | Merge via |
|--------|------------|-----------|
| `main` | Blocked (CI bot whitelisted) | PR merge only |
| `dev` | Blocked (CI bot whitelisted) | PR merge from feature/* |
| `rc` | Blocked (CI bot whitelisted) | Auto-created on draft PR |
| `alpha` | Blocked (CI bot whitelisted) | Manual rename |
| `beta` | Blocked (CI bot whitelisted) | Manual rename |
| `feature/*` | Open | N/A (source branch) |
## Version Policy
### Format
All versions use `XX.YY.ZZ` — three two-digit segments, zero-padded:
- **XX** — Major version (breaking changes)
- **YY** — Minor version (new features, bumped on release to main)
- **ZZ** — Patch version (auto-incremented on every push to dev/feature branches)
Rollover: patch `99` → `00` increments minor; minor `99` → `00` increments major.
### Stability suffixes
Each branch appends a suffix to indicate stability:
| Branch | Suffix | Example |
|--------|--------|---------|
| `main` | (none) | `02.09.00` |
| `dev` | `-dev` | `02.09.01-dev` |
| `feature/*` | `-dev` | `02.09.01-dev` |
| `alpha` | `-alpha` | `02.09.01-alpha` |
| `beta` | `-beta` | `02.09.01-beta` |
| `rc` | `-rc` | `02.09.01-rc` |
### Auto version bump
On every push to `dev`, `feature/*`, or `patch/*`:
1. Patch version incremented
2. Stability suffix `-dev` applied
3. All version-bearing files updated (manifests, CHANGELOG, PHP headers, etc.)
4. Commit created with `[skip ci]` to avoid loops
### Release version flow
Version bumps happen at specific release events:
| Event | Bump | Example |
|-------|------|---------|
| Feature merged to dev | Patch bump after dev release | `02.09.01-dev` → release → `02.09.02-dev` |
| Dev promoted to RC | Minor bump | `02.09.02-dev` → `02.10.00-rc` |
| RC merged to main | Minor bump | `02.10.00-rc` → `02.11.00` (stable) |
| Dev recreated from main | Patch bump | `02.11.00` → `02.11.01-dev` |
### Release stream copies
When a higher-stability release is published, copies are created for all lesser streams with the same base version:
- **RC `02.10.00-rc`** also creates: `02.10.00-dev`, `02.10.00-alpha`, `02.10.00-beta`
- **Stable `02.11.00`** also creates: `02.11.00-dev`, `02.11.00-alpha`, `02.11.00-beta`, `02.11.00-rc`
This ensures Joomla sites on ANY stability channel see the update (Joomla only shows versions higher than what's installed).
### Version files
The version tools update all files containing version stamps:
- `.mokogitea/manifest.xml` (canonical source)
- Joomla XML manifests (`<version>` tag)
- `README.md`, `CHANGELOG.md` (`VERSION:` pattern)
- `package.json`, `pyproject.toml`
- Any text file with a `VERSION: XX.YY.ZZ` label
Files synced from other repos (with a `# REPO:` header) are not touched.
## Code Standards
- **PHP**: PSR-12, tabs for indentation
- **Copyright**: all files must include the Moko Consulting copyright header
- **License**: SPDX identifier `GPL-3.0-or-later` (or as specified per repo)
- **Attribution**: use `Authored-by: Moko Consulting` in commits, not individual names
## Commit Messages
Use conventional commit format:
```
type(scope): short description
Optional body with context.
Authored-by: Moko Consulting
```
Types: `feat`, `fix`, `chore`, `docs`, `style`, `refactor`, `test`, `ci`
Special flags in commit messages:
- `[skip ci]` — skip all CI workflows
- `[skip bump]` — skip auto version bump only
## Reporting Issues
Use the repository's issue tracker with the appropriate template.
---
*Moko Consulting <hello@mokoconsulting.tech>*
# Contributing to Moko Consulting Projects
Thank you for your interest in contributing. All Moko Consulting repositories follow this universal workflow and version policy.
## Branching Workflow
```
feature/* ──PR──> dev ──draft PR──> (renamed to rc) ──merge──> main
```
### Step by step
1. **Create a feature branch** from `dev`:
```bash
git checkout dev && git pull
git checkout -b feature/my-change
```
2. **Work and commit** on your feature branch. Push to origin.
3. **Open a PR**: `feature/my-change` → `dev`. After review and checks, merge it.
4. **When ready for release**, open a **draft PR**: `dev` → `main`.
- This automatically renames the source branch to `rc` (release candidate)
- An RC pre-release is built and uploaded
5. **Alpha and beta branches** are created by manually renaming the branch before the RC stage:
- Rename `dev` to `alpha` for early testing → alpha pre-release is built
- Rename `alpha` to `beta` for feature-complete testing → beta pre-release is built
- When the draft PR is created, the branch is renamed to `rc`
6. **Once PR checks pass** on the `rc` branch, mark the PR as ready and merge to `main`.
7. **Merging to main** triggers the stable release pipeline:
- Minor version bump (e.g., `02.09.xx` → `02.10.00`)
- Stability suffix stripped (clean version)
- Gitea release created with ZIP/tar.gz packages
- `updates.xml` updated (Joomla extensions)
- `dev` branch recreated from `main`
### Branch summary
| Branch | Purpose | Created by |
|--------|---------|-----------|
| `feature/*` | New features and fixes | Developer |
| `dev` | Integration branch | Auto-recreated after release |
| `alpha` | Alpha pre-release testing | Manual rename from `dev` |
| `beta` | Beta pre-release testing | Manual rename from `alpha` |
| `rc` | Release candidate | Auto-renamed on draft PR to main |
| `main` | Stable releases | Protected, merge only |
| `version/XX.YY.ZZ` | Archived release snapshots | Auto-created by CI |
### Protected branches
| Branch | Direct push | Merge via |
|--------|------------|-----------|
| `main` | Blocked (CI bot whitelisted) | PR merge only |
| `dev` | Blocked (CI bot whitelisted) | PR merge from feature/* |
| `rc` | Blocked (CI bot whitelisted) | Auto-created on draft PR |
| `alpha` | Blocked (CI bot whitelisted) | Manual rename |
| `beta` | Blocked (CI bot whitelisted) | Manual rename |
| `feature/*` | Open | N/A (source branch) |
## Version Policy
### Format
All versions use `XX.YY.ZZ` — three two-digit segments, zero-padded:
- **XX** — Major version (breaking changes)
- **YY** — Minor version (new features, bumped on release to main)
- **ZZ** — Patch version (auto-incremented on every push to dev/feature branches)
Rollover: patch `99` → `00` increments minor; minor `99` → `00` increments major.
### Stability suffixes
Each branch appends a suffix to indicate stability:
| Branch | Suffix | Example |
|--------|--------|---------|
| `main` | (none) | `02.09.00` |
| `dev` | `-dev` | `02.09.01-dev` |
| `feature/*` | `-dev` | `02.09.01-dev` |
| `alpha` | `-alpha` | `02.09.01-alpha` |
| `beta` | `-beta` | `02.09.01-beta` |
| `rc` | `-rc` | `02.09.01-rc` |
### Auto version bump
On every push to `dev`, `feature/*`, or `patch/*`:
1. Patch version incremented
2. Stability suffix `-dev` applied
3. All version-bearing files updated (manifests, CHANGELOG, PHP headers, etc.)
4. Commit created with `[skip ci]` to avoid loops
### Release version flow
Version bumps happen at specific release events:
| Event | Bump | Example |
|-------|------|---------|
| Feature merged to dev | Patch bump after dev release | `02.09.01-dev` → release → `02.09.02-dev` |
| Dev promoted to RC | Minor bump | `02.09.02-dev` → `02.10.00-rc` |
| RC merged to main | Minor bump | `02.10.00-rc` → `02.11.00` (stable) |
| Dev recreated from main | Patch bump | `02.11.00` → `02.11.01-dev` |
### Release stream copies
When a higher-stability release is published, copies are created for all lesser streams with the same base version:
- **RC `02.10.00-rc`** also creates: `02.10.00-dev`, `02.10.00-alpha`, `02.10.00-beta`
- **Stable `02.11.00`** also creates: `02.11.00-dev`, `02.11.00-alpha`, `02.11.00-beta`, `02.11.00-rc`
This ensures Joomla sites on ANY stability channel see the update (Joomla only shows versions higher than what's installed).
### Version files
The version tools update all files containing version stamps:
- `.mokogitea/manifest.xml` (canonical source)
- Joomla XML manifests (`<version>` tag)
- `README.md`, `CHANGELOG.md` (`VERSION:` pattern)
- `package.json`, `pyproject.toml`
- Any text file with a `VERSION: XX.YY.ZZ` label
Files synced from other repos (with a `# REPO:` header) are not touched.
## Code Standards
- **PHP**: PSR-12, tabs for indentation
- **Copyright**: all files must include the Moko Consulting copyright header
- **License**: SPDX identifier `GPL-3.0-or-later` (or as specified per repo)
- **Attribution**: use `Authored-by: Moko Consulting` in commits, not individual names
## Commit Messages
Use conventional commit format:
```
type(scope): short description
Optional body with context.
Authored-by: Moko Consulting
```
Types: `feat`, `fix`, `chore`, `docs`, `style`, `refactor`, `test`, `ci`
Special flags in commit messages:
- `[skip ci]` — skip all CI workflows
- `[skip bump]` — skip auto version bump only
## Reporting Issues
Use the repository's issue tracker with the appropriate template.
---
*Moko Consulting <hello@mokoconsulting.tech>*
PLUGIN_SCRIPTS.md
+4 -4
View File
@@ -2,16 +2,16 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Root
INGROUP: MokoPlatform
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Root
INGROUP: MokoCLI
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /PLUGIN_SCRIPTS.md
BRIEF: Plugin system CLI documentation
-->
# Plugin System CLI Scripts
Command-line scripts for validating, health checking, and managing projects using the moko-platform plugin system.
Command-line scripts for validating, health checking, and managing projects using the MokoCLI plugin system.
## Available Scripts
README.md
+5 -5
View File
@@ -2,19 +2,19 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Root
INGROUP: MokoPlatform
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Root
INGROUP: MokoCLI
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /README.md
VERSION: 09.25.05
BRIEF: Project overview and documentation
-->
# moko-platform Enterprise API
# MokoCLI Enterprise API
![Version](https://img.shields.io/badge/version-09.01.00-blue) ![PHP](https://img.shields.io/badge/PHP-8.1%2B-777BB4) ![License](https://img.shields.io/badge/license-GPL--3.0--or--later-green)
PHP implementation of moko-platform — enterprise standards, automation framework, workflow templates, and bulk sync tooling.
PHP implementation of MokoCLI — enterprise standards, automation framework, workflow templates, and bulk sync tooling.
> **Primary platform**: [Gitea — git.mokoconsulting.tech](https://git.mokoconsulting.tech/MokoConsulting/MokoStandards-API)
> **Backup mirror**: [GitHub](https://github.com/MokoConsulting/MokoStandards-API) *(read-only mirror)*
analysis/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Analysis
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Analysis
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /analysis/index.md
BRIEF: Analysis directory index
-->
automation/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Automation
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Automation
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /automation/index.md
BRIEF: Automation directory index
-->
fix/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Fix
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Fix
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /fix/index.md
BRIEF: Fix directory index
-->
index.md
+6 -6
View File
@@ -2,16 +2,16 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Root
INGROUP: MokoPlatform
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Root
INGROUP: MokoCLI
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /index.md
BRIEF: Scripts directory index
-->
# Scripts Index
Quick navigation for moko-platform scripts organized by function.
Quick navigation for MokoCLI scripts organized by function.
## Core Categories
@@ -60,7 +60,7 @@ Shared library code
- Extension utilities
- GitHub client
### [Wiki](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/wiki)
### [Wiki](https://git.mokoconsulting.tech/MokoConsulting/mokocli/wiki)
All documentation lives in the Gitea wiki.
### [Tests](tests/)
@@ -93,4 +93,4 @@ All three languages may coexist in the same directory for the same functionality
## See Also
- [README.md](README.md) - Comprehensive scripts documentation
- [Wiki](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/wiki) - Documentation (wiki-first)
- [Wiki](https://git.mokoconsulting.tech/MokoConsulting/mokocli/wiki) - Documentation (wiki-first)
lib/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Lib
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Lib
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /lib/index.md
BRIEF: Library directory index
-->
maintenance/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Maintenance
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Maintenance
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /maintenance/index.md
BRIEF: Maintenance directory index
-->
templates/configs/README.md
+7 -7
View File
@@ -6,16 +6,16 @@ This file is part of a Moko Consulting project.
SPDX-License-Identifier: GPL-3.0-or-later
# FILE INFORMATION
DEFGROUP: MokoPlatform.Templates
INGROUP: MokoPlatform
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Templates
INGROUP: MokoCLI
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/configs/README.md
BRIEF: Code quality and security tool configuration templates
-->
# Code Quality Configuration Templates
This directory contains standardized configuration files for code quality, linting, and security tools used across moko-platform projects.
This directory contains standardized configuration files for code quality, linting, and security tools used across MokoCLI projects.
## Available Configurations
@@ -296,9 +296,9 @@ These tools work seamlessly with:
## Support and Updates
Configuration templates are maintained in the moko-platform repository:
- **Repository**: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
- **Documentation**: https://git.mokoconsulting.tech/MokoConsulting/moko-platform/tree/main/docs
Configuration templates are maintained in the MokoCLI repository:
- **Repository**: https://git.mokoconsulting.tech/MokoConsulting/mokocli
- **Documentation**: https://git.mokoconsulting.tech/MokoConsulting/mokocli/tree/main/docs
- **Issues**: Report problems or suggest improvements via GitHub Issues
## Version History
templates/configs/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Configs
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Configs
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/configs/index.md
BRIEF: Configuration templates directory index
-->
templates/docs/README.md
+4 -4
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Docs
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Docs
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/docs/README.md
BRIEF: Documentation templates README
-->
@@ -13,7 +13,7 @@ BRIEF: Documentation templates README
## Purpose
This directory contains governed documentation templates for the moko-platform organization. These templates ensure consistency, completeness, and compliance across all documentation artifacts.
This directory contains governed documentation templates for the MokoCLI organization. These templates ensure consistency, completeness, and compliance across all documentation artifacts.
## Intended Use
templates/docs/extra/README.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Docs.Extra
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Docs.Extra
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/docs/extra/README.md
BRIEF: Extra documentation templates README
-->
templates/docs/extra/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Docs.Extra
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Docs.Extra
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/docs/extra/index.md
BRIEF: Extra documentation templates directory index
-->
templates/docs/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Docs
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Docs
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/docs/index.md
BRIEF: Documentation templates directory index
-->
templates/docs/required/GOVERNANCE.md
+8 -8
View File
@@ -17,14 +17,14 @@
FILE INFORMATION
DEFGROUP: {{org}}.{{repo_name}}
INGROUP: MokoPlatform.Governance
INGROUP: MokoCLI.Governance
REPO: https://github.com/{{org}}/{{repo_name}}
VERSION: {{standards_version}}
PATH: /GOVERNANCE.md
BRIEF: Project governance rules, roles, and decision process for {{repo_name}}
-->
[![moko-platform](https://img.shields.io/badge/moko--platform-{{standards_version}}-blue)](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)
[![MokoCLI](https://img.shields.io/badge/moko--platform-{{standards_version}}-blue)](https://git.mokoconsulting.tech/MokoConsulting/mokocli)
# Project Governance
@@ -32,10 +32,10 @@
This document defines the governance model for the `{{repo_name}}` repository within the
`{{org}}` organization. It is automatically maintained by
[moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform) v{{standards_version}}.
[MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli) v{{standards_version}}.
Full governance policy is defined in the moko-platform source repository:
[docs/policy/GOVERNANCE.md](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/policy/GOVERNANCE.md)
Full governance policy is defined in the MokoCLI source repository:
[docs/policy/GOVERNANCE.md](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/policy/GOVERNANCE.md)
---
@@ -80,7 +80,7 @@ available. The following requirements remain mandatory regardless:
4. **Documentation** — changes are documented in `CHANGELOG.md`.
See the full policy:
[Sole Operator Policy](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/policy/GOVERNANCE.md#sole-operator-policy)
[Sole Operator Policy](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/policy/GOVERNANCE.md#sole-operator-policy)
---
@@ -113,7 +113,7 @@ See the full policy:
| Applies To | {{org}}/{{repo_name}} |
| Jurisdiction | Tennessee, USA |
| Maintainer | @mokoconsulting-tech |
| Standards | moko-platform v{{standards_version}} |
| Standards | MokoCLI v{{standards_version}} |
| Repo | https://github.com/{{org}}/{{repo_name}} |
| Path | /GOVERNANCE.md |
| Status | Active — auto-maintained by moko-platform |
| Status | Active — auto-maintained by MokoCLI |
templates/docs/required/README.md
+4 -4
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Docs.Required
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Docs.Required
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/docs/required/README.md
BRIEF: Required documentation templates README
-->
@@ -13,7 +13,7 @@ BRIEF: Required documentation templates README
## Purpose
This directory contains mandatory documentation templates that MUST be present in all repositories governed by moko-platform documentation policies. These templates ensure baseline documentation compliance and organizational consistency.
This directory contains mandatory documentation templates that MUST be present in all repositories governed by MokoCLI documentation policies. These templates ensure baseline documentation compliance and organizational consistency.
## Intended Use
templates/docs/required/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Docs.Required
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Docs.Required
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/docs/required/index.md
BRIEF: Required documentation templates directory index
-->
templates/docs/required/template-CONTRIBUTING.md
+14 -14
View File
@@ -24,7 +24,7 @@
Thank you for your interest in contributing to **{{REPO_NAME}}**!
This repository is governed by **[moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)** — the authoritative source of coding standards, workflows, and policies for all Moko Consulting repositories.
This repository is governed by **[MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli)** — the authoritative source of coding standards, workflows, and policies for all Moko Consulting repositories.
## Branch Strategy
@@ -49,9 +49,9 @@ This repository is governed by **[moko-platform](https://git.mokoconsulting.tech
|--------|-----|
| `dev/XX.YY.ZZ` | Feature development (e.g., `dev/02.00.00/add-extrafields`) |
| `version/XX` | Stable release (auto-created, never manually pushed) |
| `chore/` | Automated sync branches (managed by moko-platform) |
| `chore/` | Automated sync branches (managed by MokoCLI) |
> **Never use** `feature/`, `hotfix/`, or `release/` prefixes — they are not part of the moko-platform branch strategy.
> **Never use** `feature/`, `hotfix/`, or `release/` prefixes — they are not part of the MokoCLI branch strategy.
## Commit Conventions
@@ -84,16 +84,16 @@ When your PR is merged to `main`, these workflows run automatically:
## Coding Standards
All contributions must follow [moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform):
All contributions must follow [MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli):
| Standard | Reference |
|----------|-----------|
| Coding Style | [coding-style-guide.md](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/policy/coding-style-guide.md) |
| File Headers | [file-header-standards.md](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/policy/file-header-standards.md) |
| Branching | [branch-release-strategy.md](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/policy/branch-release-strategy.md) |
| Merge Strategy | [merge-strategy.md](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/policy/merge-strategy.md) |
| Scripting | [scripting-standards.md](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/policy/scripting-standards.md) |
| Build & Release | [build-release.md](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/workflows/build-release.md) |
| Coding Style | [coding-style-guide.md](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/policy/coding-style-guide.md) |
| File Headers | [file-header-standards.md](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/policy/file-header-standards.md) |
| Branching | [branch-release-strategy.md](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/policy/branch-release-strategy.md) |
| Merge Strategy | [merge-strategy.md](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/policy/merge-strategy.md) |
| Scripting | [scripting-standards.md](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/policy/scripting-standards.md) |
| Build & Release | [build-release.md](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/workflows/build-release.md) |
## PR Checklist
@@ -109,12 +109,12 @@ All contributions must follow [moko-platform](https://git.mokoconsulting.tech/Mo
## Custom Workflows
Place repo-specific workflows in `.mokogitea/workflows/custom/` — they are **never overwritten or deleted** by moko-platform sync:
Place repo-specific workflows in `.mokogitea/workflows/custom/` — they are **never overwritten or deleted** by MokoCLI sync:
```
.mokogitea/workflows/
├── deploy-dev.yml ← Synced from moko-platform
├── auto-release.yml ← Synced from moko-platform
├── deploy-dev.yml ← Synced from MokoCLI
├── auto-release.yml ← Synced from MokoCLI
└── custom/ ← Your custom workflows (safe)
└── my-custom-ci.yml
```
@@ -125,4 +125,4 @@ By contributing, you agree that your contributions will be licensed under the [G
---
*This file is synced from [moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform). Do not edit directly — changes will be overwritten on the next sync.*
*This file is synced from [MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli). Do not edit directly — changes will be overwritten on the next sync.*
templates/docs/required/template-README.md
+2 -2
View File
@@ -22,7 +22,7 @@ BRIEF: {{REPO_DESCRIPTION}}
# {{REPO_NAME}}
[![License: GPL v3](https://img.shields.io/badge/License-GPLv3-blue.svg)](https://www.gnu.org/licenses/gpl-3.0)
[![moko-platform](https://img.shields.io/badge/moko--platform-{{standards_version}}-orange)](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)
[![MokoCLI](https://img.shields.io/badge/moko--platform-{{standards_version}}-orange)](https://git.mokoconsulting.tech/MokoConsulting/mokocli)
> {{REPO_DESCRIPTION}}
@@ -40,7 +40,7 @@ BRIEF: {{REPO_DESCRIPTION}}
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines. This repository follows [moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform).
See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines. This repository follows [MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli).
## License
templates/docs/required/template-SECURITY.md
+3 -3
View File
@@ -130,7 +130,7 @@ Advisories include:
## Security Best Practices
For repositories adopting moko-platform:
For repositories adopting MokoCLI:
### Required Controls
@@ -188,7 +188,7 @@ See [Security Scanning Policy](docs/policy/security-scanning.md) for detailed re
## Compliance and Governance
This security policy is binding for all repositories governed by moko-platform. Deviations require documented justification and approval from the Security Owner.
This security policy is binding for all repositories governed by MokoCLI. Deviations require documented justification and approval from the Security Owner.
Security policies are reviewed and updated at least annually or following significant security incidents.
@@ -228,7 +228,7 @@ The following are explicitly out of scope:
| Repository | [REPOSITORY_URL] |
| Owner | [OWNER_NAME] |
| Scope | Security vulnerability handling |
| Applies To | All repositories governed by moko-platform |
| Applies To | All repositories governed by MokoCLI |
| Status | Active |
| Effective | [YYYY-MM-DD] |
templates/index.md
+8 -8
View File
@@ -19,18 +19,18 @@ You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
# FILE INFORMATION
DEFGROUP: MokoPlatform.Templates
INGROUP: MokoPlatform
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Templates
INGROUP: MokoCLI
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/index.md
BRIEF: Comprehensive catalog of all templates in moko-platform
BRIEF: Comprehensive catalog of all templates in MokoCLI
-->
# Templates Catalog
## Overview
This directory contains all templates and reference implementations provided by moko-platform. Templates are non-authoritative examples that demonstrate how to implement the standards defined in `/docs/policy/`.
This directory contains all templates and reference implementations provided by MokoCLI. Templates are non-authoritative examples that demonstrate how to implement the standards defined in `/docs/policy/`.
## Purpose
@@ -102,7 +102,7 @@ Configuration file templates for common tools.
### Documentation (`docs/`)
Documentation file templates aligned with moko-platform policies.
Documentation file templates aligned with MokoCLI policies.
**Templates:**
- `README.md.template` - Repository README template
@@ -396,7 +396,7 @@ To deprecate a template:
### Getting Help
- Browse existing templates for examples
- Review moko-platform repository as reference implementation
- Review MokoCLI repository as reference implementation
- Consult with repository maintainers
- Submit issues for template problems or requests
@@ -416,7 +416,7 @@ To contribute new templates or improvements:
## Metadata
* **Document**: templates/index.md
* **Repository**: [moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)
* **Repository**: [MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli)
* **Owner**: Moko Consulting Engineering Team
* **Scope**: Template catalog and usage guide
* **Lifecycle**: Active
templates/licenses/README.md
+7 -7
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Licenses
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Licenses
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/licenses/README.md
BRIEF: License templates README
-->
@@ -73,7 +73,7 @@ The following license files are maintained as authoritative sources:
1. **Copy the license file** to your repository root:
```bash
# From your repository root
cp /path/to/moko-platform/templates/licenses/GPL-3.0 ./LICENSE
cp /path/to/MokoCLI/templates/licenses/GPL-3.0 ./LICENSE
```
2. **No file extension**: The LICENSE file must not have an extension (use `LICENSE`, not `LICENSE.txt` or `LICENSE.md`)
@@ -173,7 +173,7 @@ along with this program. If not, see <https://www.gnu.org/licenses/>.
```bash
# Check if your LICENSE matches the authoritative version
diff LICENSE /path/to/moko-platform/templates/licenses/GPL-3.0
diff LICENSE /path/to/MokoCLI/templates/licenses/GPL-3.0
# Calculate checksum for verification
sha256sum LICENSE
@@ -193,7 +193,7 @@ The repository health workflow automatically verifies:
- [SPDX License List](https://spdx.org/licenses/)
- [Choose a License](https://choosealicense.com/)
- [GPL Compliance Guide](https://www.gnu.org/licenses/gpl-compliance.html)
- [moko-platform License Policy](../../docs/policy/license-compliance.md)
- [MokoCLI License Policy](../../docs/policy/license-compliance.md)
## Maintenance
@@ -213,4 +213,4 @@ The repository health workflow automatically verifies:
For questions about license selection or compliance:
- **Email**: legal@mokoconsulting.tech
- **Documentation**: See [License Compliance Policy](../../docs/policy/license-compliance.md)
- **Issues**: Open an issue in moko-platform repository
- **Issues**: Open an issue in MokoCLI repository
templates/licenses/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Licenses
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Licenses
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/licenses/index.md
BRIEF: License templates directory index
-->
templates/makefiles/README.md
+4 -4
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Makefiles
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Makefiles
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/makefiles/README.md
BRIEF: Makefile templates README
-->
@@ -98,6 +98,6 @@ Platform-specific templates may include additional targets relevant to their eco
## Support
For questions or issues with Makefile templates:
- See main moko-platform documentation
- See main MokoCLI documentation
- Check the platform-specific guides (Joomla, Dolibarr)
- Review the schema documentation for source/destination details
templates/mokogitea/ISSUE_TEMPLATE/documentation.md
+1 -1
View File
@@ -42,7 +42,7 @@ Suggested text here
<!-- Add any other context, screenshots, or references -->
## Standards Alignment
- [ ] Follows moko-platform documentation guidelines
- [ ] Follows MokoCLI documentation guidelines
- [ ] Uses en_US/en_GB localization
- [ ] Includes proper SPDX headers where applicable
templates/mokogitea/ISSUE_TEMPLATE/dolibarr_module_id_request.md
+3 -3
View File
@@ -92,7 +92,7 @@ List Dolibarr hooks this module will use:
### ID Range Preference
Based on the [Dolibarr Module ID Policy](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/policy/DOLIBARR_MODULE_ID_REQUEST.md):
Based on the [Dolibarr Module ID Policy](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/policy/DOLIBARR_MODULE_ID_REQUEST.md):
**Preferred Range** (will be assigned by coordinator):
- [ ] Internal module (100000-109999)
@@ -104,7 +104,7 @@ Based on the [Dolibarr Module ID Policy](https://git.mokoconsulting.tech/MokoCon
### Security and Compliance
**For Public Modules** (required before external registration):
- [ ] Code follows moko-platform
- [ ] Code follows MokoCLI
- [ ] Security review completed
- [ ] No sensitive data or credentials in code
- [ ] License properly defined (GPL-3.0-or-later)
@@ -143,7 +143,7 @@ If similar modules exist, explain why a new module is needed:
### Acknowledgments
- [ ] I have read the [Dolibarr Module ID Policy](https://git.mokoconsulting.tech/MokoConsulting/moko-platform/blob/main/docs/policy/DOLIBARR_MODULE_ID_REQUEST.md)
- [ ] I have read the [Dolibarr Module ID Policy](https://git.mokoconsulting.tech/MokoConsulting/mokocli/blob/main/docs/policy/DOLIBARR_MODULE_ID_REQUEST.md)
- [ ] I understand internal modules use range 100000-119999
- [ ] I understand public modules require external registration with Dolibarr Foundation
- [ ] I understand module IDs are never reused once allocated
templates/mokogitea/ISSUE_TEMPLATE/feature_request.md
+1 -1
View File
@@ -37,7 +37,7 @@ If you have ideas about how this could be implemented, share them here:
Add any other context, mockups, or screenshots about the feature request here.
## Relevant Standards
Does this relate to any standards in [moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)?
Does this relate to any standards in [MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli)?
- [ ] Accessibility (WCAG 2.1 AA)
- [ ] Localization (en_US/en_GB)
- [ ] Security best practices
templates/mokogitea/ISSUE_TEMPLATE/security.md
+1 -1
View File
@@ -35,7 +35,7 @@ Use this template only for:
<!-- Describe how this could be addressed -->
## Standards Reference
Does this relate to security standards in [moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)?
Does this relate to security standards in [MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli)?
- [ ] SPDX license identifiers
- [ ] Secret management
- [ ] Dependency security
templates/mokogitea/README.md
+7 -7
View File
@@ -19,9 +19,9 @@ You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
# FILE INFORMATION
DEFGROUP: MokoPlatform.Templates
INGROUP: MokoPlatform.GitHub
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Templates
INGROUP: MokoCLI.GitHub
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/mokogitea/README.md
BRIEF: GitHub-specific templates including issues, PRs, and CODEOWNERS
-->
@@ -149,10 +149,10 @@ your-repository/
blank_issues_enabled: false
contact_links:
- name: "📚 Documentation"
url: https://git.mokoconsulting.tech/MokoConsulting/moko-platform/docs
url: https://git.mokoconsulting.tech/MokoConsulting/mokocli/docs
about: "Check the documentation first"
- name: "💬 Discussions"
url: https://git.mokoconsulting.tech/MokoConsulting/moko-platform/discussions
url: https://git.mokoconsulting.tech/MokoConsulting/mokocli/discussions
about: "Ask questions and discuss ideas"
```
@@ -367,12 +367,12 @@ Require status checks that verify:
- [GitHub Issue Templates Documentation](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository)
- [GitHub PR Templates Documentation](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository)
- [GitHub CODEOWNERS Documentation](https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners)
- [moko-platform Repository](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)
- [MokoCLI Repository](https://git.mokoconsulting.tech/MokoConsulting/mokocli)
## Metadata
* **Document**: templates/mokogitea/README.md
* **Repository**: [moko-platform](https://git.mokoconsulting.tech/MokoConsulting/moko-platform)
* **Repository**: [MokoCLI](https://git.mokoconsulting.tech/MokoConsulting/mokocli)
* **Owner**: Moko Consulting Engineering Team
* **Scope**: GitHub templates and configuration
* **Lifecycle**: Active
templates/required/README.md
+20 -20
View File
@@ -2,20 +2,20 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Required
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Required
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/required/README.md
BRIEF: Required templates README
-->
# Required Templates
This directory contains **REQUIRED** files that must be present in all moko-platform-compliant repositories.
This directory contains **REQUIRED** files that must be present in all MokoCLI-compliant repositories.
## Overview
Required templates are essential files that provide core functionality and ensure consistency across all repositories in the organization. These files must be copied to target repositories and kept synchronized with moko-platform updates.
Required templates are essential files that provide core functionality and ensure consistency across all repositories in the organization. These files must be copied to target repositories and kept synchronized with MokoCLI updates.
## Required Files
@@ -28,11 +28,11 @@ Required templates are essential files that provide core functionality and ensur
**Installation**:
```bash
# Quick install
curl -fsSL https://raw.githubusercontent.com/MokoConsulting/moko-platform/main/templates/required/setup-labels.sh > scripts/maintenance/setup-labels.sh
curl -fsSL https://raw.githubusercontent.com/MokoConsulting/MokoCLI/main/templates/required/setup-labels.sh > scripts/maintenance/setup-labels.sh
chmod +x scripts/maintenance/setup-labels.sh
# Or copy from moko-platform
cp /path/to/moko-platform/templates/required/setup-labels.sh scripts/maintenance/setup-labels.sh
# Or copy from MokoCLI
cp /path/to/MokoCLI/templates/required/setup-labels.sh scripts/maintenance/setup-labels.sh
chmod +x scripts/maintenance/setup-labels.sh
```
@@ -50,7 +50,7 @@ chmod +x scripts/maintenance/setup-labels.sh
- Project types (joomla, dolibarr, generic)
- Languages (php, javascript, typescript, python, css, html)
- Components (documentation, ci-cd, docker, tests, security, dependencies, config, build)
- Workflow (automation, moko-platform, needs-review, work-in-progress, breaking-change)
- Workflow (automation, MokoCLI, needs-review, work-in-progress, breaking-change)
- Priority (critical, high, medium, low)
- Type (bug, feature, enhancement, refactor, chore)
- Status (pending, in-progress, blocked, on-hold, wontfix)
@@ -95,10 +95,10 @@ done
### Automated Compliance
Use the moko-platform validation scripts:
Use the MokoCLI validation scripts:
```bash
# From moko-platform repository
# From MokoCLI repository
python3 scripts/validate/validate_repo_health.py --check-required-files
# Or use bulk validation
@@ -107,14 +107,14 @@ php scripts/automation/bulk_update_repos.php --validate-only
## Syncing Updates
Required files should be kept in sync with moko-platform:
Required files should be kept in sync with MokoCLI:
```bash
# Update single file
curl -fsSL https://raw.githubusercontent.com/MokoConsulting/moko-platform/main/templates/required/setup-labels.sh > scripts/maintenance/setup-labels.sh
curl -fsSL https://raw.githubusercontent.com/MokoConsulting/MokoCLI/main/templates/required/setup-labels.sh > scripts/maintenance/setup-labels.sh
# Or use bulk sync
cd /path/to/moko-platform
cd /path/to/MokoCLI
./scripts/automation/bulk_update_repos.sh --org MokoConsulting --sync-required
```
@@ -123,26 +123,26 @@ cd /path/to/moko-platform
To deploy required files to a repository using GitHub Copilot:
```markdown
Deploy required moko-platform files to this repository.
Deploy required MokoCLI files to this repository.
Required files to deploy:
1. setup-labels.sh - Label deployment script
Process:
1. Create scripts/maintenance/ directory if not exists
2. Download setup-labels.sh from MokoConsulting/moko-platform
2. Download setup-labels.sh from MokoConsulting/MokoCLI
3. Copy to scripts/maintenance/setup-labels.sh
4. Make executable: chmod +x scripts/maintenance/setup-labels.sh
5. Test with dry-run: ./scripts/maintenance/setup-labels.sh --dry-run
6. Deploy labels: ./scripts/maintenance/setup-labels.sh
7. Verify labels in repository settings
Source: https://git.mokoconsulting.tech/MokoConsulting/moko-platform/tree/main/templates/required
Source: https://git.mokoconsulting.tech/MokoConsulting/mokocli/tree/main/templates/required
```
## Future Required Files
As moko-platform evolves, additional required files may be added:
As MokoCLI evolves, additional required files may be added:
- **PLANNED**: `.github/labeler.yml` - Auto-labeling configuration
- **PLANNED**: `.editorconfig` - Editor configuration
@@ -153,7 +153,7 @@ As moko-platform evolves, additional required files may be added:
- **Documentation**: [Copilot Sync Standards Guide](../../docs/guide/copilot-sync-standards.md)
- **Label Guide**: [Label Deployment Guide](../../docs/guides/label-deployment.md)
- **Issues**: https://git.mokoconsulting.tech/MokoConsulting/moko-platform/issues
- **Issues**: https://git.mokoconsulting.tech/MokoConsulting/mokocli/issues
- **Contact**: hello@mokoconsulting.tech
## Related Documentation
@@ -167,4 +167,4 @@ As moko-platform evolves, additional required files may be added:
**Last Updated**: 2026-01-28
**Version**: 03.01.00
**Maintained By**: moko-platform Team
**Maintained By**: MokoCLI Team
templates/schemas/README.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Schemas
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Schemas
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/schemas/README.md
BRIEF: Schema templates README
-->
templates/schemas/schemas/README.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Schemas
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Schemas
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/schemas/schemas/README.md
BRIEF: Deprecated schema directory README
-->
templates/scripts/README.md
+4 -4
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Scripts
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Scripts
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/scripts/README.md
BRIEF: Script templates README
-->
@@ -116,7 +116,7 @@ These are template scripts. Adapt them to your project's specific needs:
## Standards Compliance
All scripts follow moko-platform requirements:
All scripts follow MokoCLI requirements:
- SPDX license headers
- GPL-3.0-or-later license
templates/scripts/fix/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Scripts.Fix
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Scripts.Fix
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/scripts/fix/index.md
BRIEF: Fix scripts directory index
-->
templates/scripts/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Scripts
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Scripts
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/scripts/index.md
BRIEF: Script templates directory index
-->
templates/scripts/release/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Scripts.Release
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Scripts.Release
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/scripts/release/index.md
BRIEF: Release scripts directory index
-->
templates/scripts/sftp-config/README.md
+10 -10
View File
@@ -6,9 +6,9 @@ This file is part of a Moko Consulting project.
SPDX-License-Identifier: GPL-3.0-or-later
# FILE INFORMATION
DEFGROUP: MokoPlatform.Templates.Scripts
INGROUP: MokoPlatform.Templates
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Templates.Scripts
INGROUP: MokoCLI.Templates
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/scripts/sftp-config/README.md
BRIEF: Setup guide for local SFTP deployment configuration files
-->
@@ -26,14 +26,14 @@ GitHub Actions workflows.
## Quick Setup
1. **Copy the example templates** from moko-platform:
1. **Copy the example templates** from MokoCLI:
```bash
# From your repo root
mkdir -p scripts/sftp-config scripts/keys
cp path/to/moko-platform/templates/scripts/deploy/sftp-config.dev.json.example \
cp path/to/MokoCLI/templates/scripts/deploy/sftp-config.dev.json.example \
scripts/sftp-config/sftp-config.dev.json
cp path/to/moko-platform/templates/scripts/deploy/sftp-config.rs.json.example \
cp path/to/MokoCLI/templates/scripts/deploy/sftp-config.rs.json.example \
scripts/sftp-config/sftp-config.rs.json
```
@@ -76,21 +76,21 @@ GitHub Actions workflows.
```bash
# Preview what would be uploaded (no connection made)
php path/to/moko-platform/api/deploy/deploy-sftp.php \
php path/to/MokoCLI/api/deploy/deploy-sftp.php \
--path . --env dev --dry-run --verbose
# Deploy src/ to dev
php path/to/moko-platform/api/deploy/deploy-sftp.php \
php path/to/MokoCLI/api/deploy/deploy-sftp.php \
--path . --env dev
# Deploy src/ to production
php path/to/moko-platform/api/deploy/deploy-sftp.php \
php path/to/MokoCLI/api/deploy/deploy-sftp.php \
--path . --env rs
```
For full option reference run:
```bash
php path/to/moko-platform/api/deploy/deploy-sftp.php --help
php path/to/MokoCLI/api/deploy/deploy-sftp.php --help
```
---
templates/scripts/validate/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Scripts.Validate
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Scripts.Validate
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/scripts/validate/index.md
BRIEF: Validate scripts directory index
-->
templates/security/README.md
+4 -4
View File
@@ -2,16 +2,16 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Templates.Security
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Templates.Security
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /templates/security/README.md
BRIEF: Security templates README
-->
# Security Templates
This directory contains security-related templates for moko-platform repositories.
This directory contains security-related templates for MokoCLI repositories.
## index.html - Directory Listing Prevention (Static)
tests/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Tests
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Tests
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /tests/index.md
BRIEF: Tests directory index
-->
validate/SECURITY_SCANNING.md
+4 -4
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Validate
INGROUP: MokoPlatform
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Validate
INGROUP: MokoCLI
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /validate/SECURITY_SCANNING.md
BRIEF: Security scanning guide
-->
@@ -15,7 +15,7 @@ BRIEF: Security scanning guide
## Overview
This guide provides instructions for implementing and using the comprehensive security scanning infrastructure required for all moko-platform repositories.
This guide provides instructions for implementing and using the comprehensive security scanning infrastructure required for all MokoCLI repositories.
## Quick Start
validate/index.md
+3 -3
View File
@@ -2,9 +2,9 @@
Copyright (C) 2026 Moko Consulting <hello@mokoconsulting.tech>
SPDX-License-Identifier: GPL-3.0-or-later
FILE INFORMATION
DEFGROUP: MokoPlatform.Index
INGROUP: MokoPlatform.Validate
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Index
INGROUP: MokoCLI.Validate
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /validate/index.md
BRIEF: Validate directory index
-->
wrappers/index.md
+4 -4
View File
@@ -6,9 +6,9 @@ This file is part of a Moko Consulting project.
SPDX-License-Identifier: GPL-3.0-or-later
# FILE INFORMATION
DEFGROUP: MokoPlatform.Wrappers
INGROUP: MokoPlatform
REPO: https://git.mokoconsulting.tech/MokoConsulting/moko-platform
DEFGROUP: MokoCLI.Wrappers
INGROUP: MokoCLI
REPO: https://git.mokoconsulting.tech/MokoConsulting/mokocli
PATH: /wrappers/index.md
BRIEF: PHP wrapper scripts — one per CLI script in api/; add logging and repo-root detection
-->
@@ -62,7 +62,7 @@ php api/wrappers/deploy_sftp.php --help
| `check_tabs.php` | `api/validate/check_tabs.php` | Check indentation consistency |
| `check_version_consistency.php` | `api/validate/check_version_consistency.php` | Check version numbers are consistent |
| `check_xml_wellformed.php` | `api/validate/check_xml_wellformed.php` | Validate XML files are well-formed |
| `scan_drift.php` | `api/validate/scan_drift.php` | Detect drift from moko-platform |
| `scan_drift.php` | `api/validate/scan_drift.php` | Detect drift from MokoCLI |
### Automation