chore: cascade main -> dev (.mokogitea -> .mokogit / MOKOGIT_TOKEN migration) #63

Open

jmiller wants to merge 21 commits from main into dev

pull from: main

merge into: :dev

:main

:dev

:rc

:fix/gate-sync-trigger

:fix/move-sync-trigger

:fix/rebrand-mokogitea

Conversation 0 Commits 21 Files Changed 14

+580 -122

jmiller commented 2026-07-16 13:03:19 +00:00

Owner

Copy Link

Copy Source

Cascades the completed MOKOGITEA->MOKOGIT migration from main into dev: removes stale .mokogitea/, adds .mokogit/, repoints MOKOGITEA_TOKEN->MOKOGIT_TOKEN.

Cascades the completed MOKOGITEA->MOKOGIT migration from main into dev: removes stale .mokogitea/, adds .mokogit/, repoints MOKOGITEA_TOKEN->MOKOGIT_TOKEN.

jmiller added 34 commits 2026-07-16 13:03:19 +00:00

chore(branch-protection): allow actions + moko-deploy bots on protected branches ... abe2c102fd

Adds the automation identities to the branch-protection rule definitions so
release automation can operate on protected branches:
- all rules: push_whitelist_actions_user=true + moko-deploy in push whitelist
- dev, rc: enable force-push for the bots so dev can be reset to main via a
  single `git push --force origin main:dev` (delete+recreate cannot work on a
  protected branch)
- main keeps force-push disabled

moko-deploy needs org-team write access to take effect (mcp-mokogitea-api#30).
Unblocks the dev-sync + version-persist fixes (Template-Generic#53).

Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i

Merge pull request 'chore(branch-protection): allow actions + moko-deploy bots on protected branches' (#49) from chore/branch-protection-bot-allowlist into main 7b86c2c16a

fix(workflows): #53 dev-cycle correctness (protection-independent) ... 718d57bd1e

- cleanup.yml: preserve dev/rc/release-line + version/* branches (skip-list was
  deleting version/* release-history branches every week)
- notify.yml: point workflow_run at the real workflow names (Universal: Build &
  Release / Joomla: Extension CI / Generic: Project CI) so release/failure ntfy
  actually fires
- ci-joomla.yml: add plain `dev` to PR triggers so Joomla CI runs on feature->dev
- pr-check.yml (Joomla): detect platform via the MokoGitea metadata API instead
  of the removed .mokogitea/manifest.xml (Joomla PR gates were silently skipping)

Refs Template-Generic#53. Dev-sync/version-bump fixes deferred until the
branch-protection provisioner rolls out (mcp-mokogitea-api#30).

Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i

Merge pull request 'fix(workflows): #53 dev-cycle correctness (protection-independent)' (#50) from fix/workflow-audit-53 into main 95ea7cee8c

feat(workflows): move dev-cascade into dedicated cascade-dev.yml ... c84fd09e18

Moves the "recreate dev from main" function out of auto-release.yml Step 11
into its own workflow, and makes it actually work on protected branches.

- cascade-dev.yml: on release-workflow completion (+ manual dispatch),
  force-push main -> dev. The bot is force-push allowlisted on dev via
  branch-protection.yml, so this works where delete+recreate could not
  (Gitea refuses to delete a protected branch). Force-push (not merge) =>
  no version-file conflicts; running after the release => dev gets the
  fully version-bumped + changelog-promoted main. Skips Template-* repos;
  concurrency-guarded.
- auto-release.yml Step 11: drop the dev delete/recreate; keep rc cleanup.

Refs Template-Generic#53; enabled by the bot allowlist (#334/#54/#49).

Claude-Session: https://claude.ai/code/session_01WbGBN9VyRK61zczYWcCQ2i

Merge pull request 'feat(workflows): move dev-cascade into dedicated cascade-dev.yml' (#51) from feat/cascade-dev-workflow into main d93c69da9d

ci(templates): gate build/CI/release/version workflows off template repos + normalize mokocli refs ... 618350dc2e

- Add 'skip on Template-*' guards to build/CI/release/version workflows so they
  don't run on the template repo itself (only on repos created from it).
- Smart-gate sync workflows to run ONLY on Template-* sources (so platform
  templates still propagate, but regular repos don't trigger sync-out).
- Normalize mokocli->MokoCLI repo/clone URLs, drop stale mokoconsulting-tech
  org slug on the git host, and mokoplatform/moko-platform->mokocli.
  (/opt/mokocli + /tmp/mokocli server paths left intact.)

Merge pull request 'ci(templates): gate Joomla CI off template repo + normalize mokocli/moko-platform refs' (#52) from fix/gate-and-normalize into main a7fe9db66c

ci(sync): smart-gate custom/workflow-sync-trigger to run only on Template-* repos 6cb36784bb

Merge fix/gate-sync-trigger: gate workflow-sync-trigger to Template-* only 4b75851412

ci(sync): move workflow-sync-trigger.yml out of custom/ to top-level (shared workflow; keeps Template-* gate) b99c4e2eb7

Merge fix/move-sync-trigger: relocate workflow-sync-trigger to .mokogitea/workflows/ 27186ef9e1

chore(branding): Gitea -> MokoGitea in workflow/doc branding (detached fork) ... 0415c25135

DEFGROUP Gitea.* -> MokoGitea.*, committer gitea-actions[bot] -> mokogitea-actions[bot],
platform prose (Gitea wiki/release/Pages/API -> MokoGitea). Preserves functional tokens:
secrets.GITEA_TOKEN/GITHUB_TOKEN, GITEA_ACTIONS_* runner env, vars.GITEA_URL/GITEA_ORG,
and the git.mokoconsulting.tech domain. Refs Template-Generic#68.

Merge fix/rebrand-mokogitea: Gitea -> MokoGitea branding (Template-Generic#68) 585e40245c

fix(ci): guard migration SQL files against exceeding the manifest version ... 8c579a2841

Rework the SQL-schema check so each component is validated against ITS OWN
manifest version instead of a single package-level version applied to every
sql/updates/mysql dir (which mis-flagged independently-versioned sub-extensions).

Add check #11: fail if any update file version exceeds its component manifest
version. This catches migration files drifting onto a different numbering lane
and getting ahead of the release version (e.g. 01.14.00.sql while the manifest
is 01.01.40) at PR time instead of surfacing as a runtime schema mismatch.

Authored-by: Moko Consulting
Claude-Session: https://claude.ai/code/session_01VXrBk7psPzJPHVuBDJwt2x

Merge pull request 'fix(ci): guard migration SQL files against exceeding the manifest version' (#53) from fix/ci-schema-version-guard into main e37c98d70d

chore: retire MokoStandards → MokoCLI/mokocli, metadata via API, add AI-client files ... add699aa60

Rebased onto current main (preserves MokoSuite + CI work). Delta:
- Retire MokoStandards/MokoStandards-Template-*/MokoStandards-API completely
- Branding MokoCLI (CamelCase) in display text; lowercase mokocli in URLs/paths
- Complete Gitea→MokoGitea prose/path cleanup where main missed it
- Metadata references → MokoGitea Metadata field (API); no committed metadata file
- Add .mokogitea/GEMINI.md + .mokogitea/MOKOAI.md; gitignore /GEMINI.md /MOKOAI.md .mokoai/

Authored-by: Moko Consulting

Merge pull request 'Rebrand: MokoGitea + MokoCLI/mokocli, metadata via API, AI-client files' (#55) from gitea-land/mokocli-mokogitea into main ba6de9f645

chore(sync): relocate workflow-sync-trigger.yml to workflows/custom/ ... 626d8f5f0d

Keeps the template-only sync workflow out of the root dir that
workflow_sync.php distributes, so it never propagates to child repos.
Still runs here (Gitea Actions executes custom/).

Merge pull request 'chore(sync): relocate workflow-sync-trigger.yml to workflows/custom/' (#56) from chore/sync-workflow-to-custom into main 26fc3e655c

chore(platform): consolidate node+mcp -> npm (metadata + sync-trigger) ... a66601b539

Authored-by: Moko Consulting

Merge pull request 'chore(platform): consolidate node+mcp -> npm' (#57) from chore/consolidate-npm-platform into main e9741bc04f

chore(ci): add standards-compliance.yml (platform standard) fa5bced3b0

Merge pull request 'chore(ci): add standards-compliance.yml (platform standard)' (#58) from chore/add-standards-compliance into main c4285ec00b

chore(ci): enable --delete-orphans in workflow sync ... 7d18a25561

Now that getRepoPlatform reads /metadata (correct platform routing) and platform templates are complete supersets, turn on orphan pruning so repos converge exactly to their template set (custom/ and custom-* preserved).

Merge pull request 'chore(ci): enable --delete-orphans in workflow sync' (#59) from chore/enable-orphan-pruning into main 4b9bc7221e

chore(sync): map renamed Template-NPM in workflow-sync-trigger ... e53b01f86f

Template-MCP was renamed to Template-NPM. Update the sync-trigger platform
case label so the cascade maps the renamed repo correctly.

Claude-Session: https://claude.ai/code/session_01DQEMmJPe61ya7HDfA6BHP8

Merge pull request 'chore(sync): map renamed Template-NPM in workflow-sync-trigger' (#60) from chore/rename-mcp-to-npm into main d057c369f9

chore(rebrand): gitea -> git (MokoGitea -> MokoGit, .mokogitea -> .mokogit) ... be81aea7c5

Case-preserving gitea->git across brand text + functional identifiers
(MOKOGITEA_TOKEN->MOKOGIT_TOKEN, GITEA_URL/ORG/REPO, gitea-actions[bot],
ntfy gitea-*). Protected: literal `.gitea` and git.mokoconsulting.tech.

WARNING: CI-breaking until the MokoGit server side is reconfigured.

Claude-Session: https://claude.ai/code/session_01DQEMmJPe61ya7HDfA6BHP8

Merge pull request 'chore(rebrand): gitea -> git (MokoGitea -> MokoGit, .mokogitea -> .mokogit)' (#61) from chore/rebrand-gitea-to-git into main 4545876d74

chore(rebrand): brand caps MokoGit -> MokoGIT ... bf94835242

Branding: the MokoGIT wordmark is caps-GIT. Corrects the display token from
MokoGit to MokoGIT (case-sensitive; lowercase path form .mokogit untouched).

Claude-Session: https://claude.ai/code/session_01DQEMmJPe61ya7HDfA6BHP8

Merge pull request 'chore(rebrand): brand caps MokoGit -> MokoGIT' (#62) from fix/brand-mokogit-caps into main ffc945ba71

fix(ci): harden issue-branch.yml against Actions injection (sync from Template-Generic) 52f809ea04

fix(ci): harden branch-cleanup.yml against Actions injection (sync from Template-Generic) 8d5f3cbe0b

jmiller added 1 commit 2026-07-17 00:22:36 +00:00

fix(ci): MokoGit rebrand of workflow refs + ci-issue-reporter injection hardening [#353] (#65) ... 6a3d2b2308

Co-authored-by: Jonathan Miller <jmiller@mokoconsulting.tech>
Co-committed-by: Jonathan Miller <jmiller@mokoconsulting.tech>

jmiller added 1 commit 2026-07-19 01:24:38 +00:00

chore: sync auto-bump.yml from Template-Generic [skip ci] cb9b763788

jmiller added 1 commit 2026-07-19 01:24:38 +00:00

chore: sync auto-release.yml from Template-Generic [skip ci] d60b8bbbe5

jmiller added 1 commit 2026-07-19 01:24:40 +00:00

chore: sync cascade-dev.yml from Template-Generic [skip ci] 3a67db23e8

jmiller added 1 commit 2026-07-19 01:24:41 +00:00

chore: sync ci-generic.yml from Template-Generic [skip ci] c7bc3bd298

jmiller added 1 commit 2026-07-19 01:24:42 +00:00

chore: sync gitleaks.yml from Template-Generic [skip ci] 5d106d8842

jmiller added 1 commit 2026-07-19 01:24:44 +00:00

chore: sync notify.yml from Template-Generic [skip ci] b3e0a79653

jmiller added 1 commit 2026-07-19 01:24:47 +00:00

chore: sync pre-release.yml from Template-Generic [skip ci] 5bbf914374

jmiller added 1 commit 2026-07-19 01:24:48 +00:00

chore: sync push-notify.yml from Template-Generic [skip ci] 7fcf2a1e4e

jmiller added 1 commit 2026-07-19 01:24:49 +00:00

chore: sync rc-revert.yml from Template-Generic [skip ci] 81c90c0eb9

jmiller added 1 commit 2026-07-19 01:24:51 +00:00

chore: sync repo-health.yml from Template-Generic [skip ci] 2526fb347a

jmiller added 1 commit 2026-07-19 01:24:52 +00:00

chore: sync version-set.yml from Template-Generic [skip ci] 099712d889

jmiller added 2 commits 2026-07-19 02:01:50 +00:00

ci(sync): sync-trigger runs-on release [skip sync] [#134] ... fa17e874f7

Authored-by: Moko Consulting

ci(sync): sync-trigger runs-on release [skip sync] [#134] (#69) 87f646b4e5

jmiller added 1 commit 2026-07-19 06:08:21 +00:00

chore: sync pre-release.yml from Template-Generic [skip ci] 3106d1aea1

jmiller added 1 commit 2026-07-19 07:53:21 +00:00

chore: sync auto-release.yml from Template-Generic [skip ci] e070048c98

jmiller added 1 commit 2026-07-19 08:11:48 +00:00

chore: sync auto-release.yml from Template-Generic [skip ci] ee9ebbcb2c

jmiller added 1 commit 2026-07-19 08:12:04 +00:00

chore: sync pre-release.yml from Template-Generic [skip ci] c5b47ae8ee

jmiller added 1 commit 2026-07-21 18:18:20 +00:00

chore: sync auto-release.yml from Template-Generic [skip ci] 4b4169043b

jmiller added 2 commits 2026-07-21 22:10:43 +00:00

chore: anchor Composer vendor ignore to /vendor/ (allow nested vendored assets) ... 9e407557b5

Authored-by: Moko Consulting

Merge pull request 'chore: anchor Composer vendor ignore to /vendor/ (allow nested vendored assets)' (#70) from git/gitignore-vendor-anchor into main 1530c6a6a9

Some required checks failed

Hide all checks

Generic: Project CI / Lint & Validate (pull_request) Has been cancelled

Details

Generic: Project CI / Tests (pull_request) Has been cancelled

Details

Joomla: Extension CI / Lint & Validate (pull_request) Has been cancelled

Details

Joomla: Extension CI / Release Readiness Check (pull_request) Has been cancelled

Details

Cascade Main -> Dev / Cascade main -> dev (push) Has been cancelled

Details

Universal: Push Notifications / push-notify (push) Has been cancelled

Details

Generic: Standards Compliance / Secret Scanning (push) Has been cancelled

Details

Generic: Standards Compliance / License Header Validation (push) Has been cancelled

Details

Generic: Standards Compliance / Repository Structure Validation (push) Has been cancelled

Details

Generic: Standards Compliance / Coding Standards Check (push) Has been cancelled

Details

Generic: Standards Compliance / Version Consistency Check (push) Has been cancelled

Details

Generic: Standards Compliance / Workflow Configuration Check (push) Has been cancelled

Details

Generic: Standards Compliance / Documentation Quality Check (push) Has been cancelled

Details

Generic: Standards Compliance / README Completeness Check (push) Has been cancelled

Details

Generic: Standards Compliance / Git Repository Hygiene (push) Has been cancelled

Details

Generic: Standards Compliance / Script Integrity Validation (push) Has been cancelled

Details

Generic: Standards Compliance / Line Length Check (push) Has been cancelled

Details

Generic: Standards Compliance / File Naming Standards (push) Has been cancelled

Details

Generic: Standards Compliance / Insecure Code Pattern Detection (push) Has been cancelled

Details

Generic: Standards Compliance / Code Complexity Analysis (push) Has been cancelled

Details

Generic: Standards Compliance / Code Duplication Detection (push) Has been cancelled

Details

Generic: Standards Compliance / Dead Code Detection (push) Has been cancelled

Details

Generic: Standards Compliance / File Size Limits (push) Has been cancelled

Details

Generic: Standards Compliance / Binary File Detection (push) Has been cancelled

Details

Generic: Standards Compliance / TODO/FIXME Tracking (push) Has been cancelled

Details

Generic: Standards Compliance / Dependency Vulnerability Scanning (push) Has been cancelled

Details

Generic: Standards Compliance / Unused Dependencies Check (push) Has been cancelled

Details

Generic: Standards Compliance / Broken Link Detection (push) Has been cancelled

Details

Generic: Standards Compliance / API Documentation Coverage (push) Has been cancelled

Details

Generic: Standards Compliance / Accessibility Check (push) Has been cancelled

Details

Generic: Standards Compliance / Performance Metrics (push) Has been cancelled

Details

Generic: Standards Compliance / Enterprise Readiness Check (push) Has been cancelled

Details

Generic: Standards Compliance / Repository Health Check (push) Has been cancelled

Details

Generic: Standards Compliance / Terraform Configuration Validation (push) Has been cancelled

Details

Universal: PR Check / Branch Policy (pull_request) Has been cancelled

Details

Universal: PR Check / Require Docs Update (pull_request) Has been cancelled

Details

Universal: PR Check / Wiki Update Reminder (pull_request) Has been cancelled

Details

Universal: PR Check / Secret Scan (pull_request) Has been cancelled

Details

Universal: PR Check / Validate PR (pull_request) Has been cancelled

Details

Joomla: Metadata Validation / Validate Joomla Metadata (pull_request) Has been cancelled

Details

Joomla: Extension CI / Tests (PHP 8.2) (pull_request) Has been cancelled

Details

Joomla: Extension CI / Tests (PHP 8.3) (pull_request) Has been cancelled

Details

Joomla: Extension CI / PHPStan Analysis (pull_request) Has been cancelled

Details

Joomla: Extension CI / Build RC Pre-Release (pull_request) Has been cancelled

Details

Generic: Standards Compliance / Compliance Summary (push) Has been cancelled

Details

Universal: PR Check / Build RC Package (pull_request) Has been cancelled

Details

Universal: PR Check / Report Issues (pull_request) Has been cancelled

Details

This pull request has changes conflicting with the target branch.

• .mokogit/workflows/auto-release.yml

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin main:main

git checkout main

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

breaking-change

Breaking API or behavior change

ci-cd

CI/CD pipeline changes

config

Configuration changes

css

CSS/styling changes

dependencies

Dependency updates

deploy-failure

Deployment failed

documentation

Documentation changes

good first issue

Good for newcomers

health-check

Repo health check result

help wanted

Extra attention needed

html

HTML/template changes

joomla

Joomla extension

major-release

Major version release

minor-release

Minor version release

mokostandards

Related to MokoStandards framework

patch-release

Patch version release

php

PHP code

push-failure

Git push operation failed

release-candidate

Release candidate build

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

version-drift

Version mismatch across files

work-in-progress

Draft or incomplete work

bug

Something is not working

duplicate

This issue or pull request already exists

enhancement

New feature

help wanted

Need some help

invalid

Something is wrong

question

More information is needed

wontfix

This won't be fixed

No labels

Priority -

Type -

Milestone

No items

No Milestone

Assignees

Clear assignees

jmiller (Jonathan Miller)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/Template-Joomla#63