Actions: .mokogit/workflows/ custom path not detected — no runs created on push (only .gitea/ indexed) #798

New Issue

2026-07-16T15:49:25Z

jmiller commented

2026-07-16 15:49:25 +00:00

Summary

MokoGIT's Actions engine no longer detects workflows in the custom .mokogit/workflows/ path. No workflow runs are created on push from that path on any repo, and the Actions API does not index those workflows. Only Gitea's native .gitea/workflows/ path works. Org-wide CI (deploys, pr-check, standards-compliance, pre-release, auto-bump, the auto-release rc-cascade) is effectively down; repos are surviving only via a temporary .gitea/workflows/ deploy bridge.

Impact

Push-triggered CI/deploys from .mokogit/workflows/ do not run.
The auto-release cascade (promote-rc, RC build, release tagging) never fires â†’ dev â†’ main PRs do not cascade.
Every repo that relies on .mokogit/workflows/ (all of them) is affected.

Evidence (repo: MokoConsulting/mokoai, plus others)

Nothing from .mokogit/ is indexed. GET /api/v1/repos/MokoConsulting/mokoai/actions/workflows returns only the 3 .gitea/workflows/deploy-*.yml bridge files â€” 0 of the ~20 .mokogit/workflows/*.yml. Same on Template-Go and .vault: 0 .mokogit/ workflows indexed.
Dispatch 404s. POST .../actions/workflows/repo-health.yml/dispatches {"ref":"dev"} â†’ HTTP 404 (the workflow is not indexed).
Push history. The last time any .mokogit/-path workflow created a run was commit 87f7a78 at 2026-07-15 01:32Z. Every push since (20+ commits) created only .gitea/workflows/deploy-dev.yml runs (the bridge). Non-deploy .mokogit/ workflows (pre-release, standards-compliance, pr-check, auto-bump) have not run since.

Likely area

The fork's support for the custom .mokogit/workflows/ actions path (workflow discovery / run-creation), or the app.ini [actions] configuration that enables it, on the running MokoGIT container. A source/config fix may exist but not be live on the deployed container (needs recreate/restart), or the setting is inactive.

Workaround in place

.gitea/workflows/deploy-{dev,rc,prod}.yml bridge files mirror the deploy workflows into Gitea's native path so pushes still deploy. These must be removed once .mokogit/ detection is restored (else deploys double-fire). See MokoConsulting/mokoai .gitea/workflows/README.md.

Ask

Restore .mokogit/workflows/ custom-path detection (workflow indexing + push run-creation + workflow_dispatch) on the running MokoGIT, so the bridge can be retired and the org CI/cascade resumes.

## Summary MokoGIT's Actions engine no longer detects workflows in the **custom `.mokogit/workflows/`** path. No workflow runs are created on push from that path on **any** repo, and the Actions API does not index those workflows. Only Gitea's native `.gitea/workflows/` path works. Org-wide CI (deploys, `pr-check`, `standards-compliance`, `pre-release`, `auto-bump`, the `auto-release` rc-cascade) is effectively down; repos are surviving only via a temporary `.gitea/workflows/` deploy bridge. ## Impact - Push-triggered CI/deploys from `.mokogit/workflows/` do not run. - The `auto-release` cascade (promote-rc, RC build, release tagging) never fires â†’ `dev â†’ main` PRs do not cascade. - Every repo that relies on `.mokogit/workflows/` (all of them) is affected. ## Evidence (repo: MokoConsulting/mokoai, plus others) 1. **Nothing from `.mokogit/` is indexed.** `GET /api/v1/repos/MokoConsulting/mokoai/actions/workflows` returns **only** the 3 `.gitea/workflows/deploy-*.yml` bridge files â€” 0 of the ~20 `.mokogit/workflows/*.yml`. Same on `Template-Go` and `.vault`: **0 `.mokogit/` workflows indexed**. 2. **Dispatch 404s.** `POST .../actions/workflows/repo-health.yml/dispatches {"ref":"dev"}` â†’ **HTTP 404** (the workflow is not indexed). 3. **Push history.** The last time any `.mokogit/`-path workflow created a run was commit `87f7a78` at **2026-07-15 01:32Z**. Every push since (20+ commits) created **only** `.gitea/workflows/deploy-dev.yml` runs (the bridge). Non-deploy `.mokogit/` workflows (`pre-release`, `standards-compliance`, `pr-check`, `auto-bump`) have not run since. ## Likely area The fork's support for the custom `.mokogit/workflows/` actions path (workflow discovery / run-creation), or the `app.ini [actions]` configuration that enables it, on the **running** MokoGIT container. A source/config fix may exist but not be live on the deployed container (needs recreate/restart), or the setting is inactive. ## Workaround in place `.gitea/workflows/deploy-{dev,rc,prod}.yml` bridge files mirror the deploy workflows into Gitea's native path so pushes still deploy. These must be **removed once `.mokogit/` detection is restored** (else deploys double-fire). See MokoConsulting/mokoai `.gitea/workflows/README.md`. ## Ask Restore `.mokogit/workflows/` custom-path detection (workflow indexing + push run-creation + `workflow_dispatch`) on the running MokoGIT, so the bridge can be retired and the org CI/cascade resumes.

jmiller referenced this issue from MokoConsulting/MokoCLI

2026-07-16 17:55:37 +00:00

Investigate broken workflow sync — repos silently lost .mokogit/workflows #350

jmiller referenced this issue from a commit

2026-07-16 17:58:17 +00:00

fix(actions): detect .mokogit/workflows; retire .mokogitea/workflows (#798)

jmiller referenced this issue from a commit

2026-07-16 17:58:17 +00:00

chore(ci): restore .mokogit/workflows from Template-Go (sync was broken)

jmiller referenced this issue from a commit

2026-07-16 18:23:34 +00:00

merge(main): promote dev to production