Promote theme fix + MokoOnyx color separation + CLI version (dev->main) #802

Merged

jmiller merged 25 commits from dev into main 2026-07-19 01:38:45 +00:00

Conversation 0 Commits 25 Files Changed 33

+30976 -40

25 Commits

Author	SHA1	Message	Date
jmiller	4e10f5f611	chore: delete orphan test-mokogit.md to resolve #802 rename/delete conflict [skip ci]	2026-07-19 01:37:26 +00:00
jmiller	56c75a656c	chore(ci): align deploy-prod.yml with main (Template-Go canonical) to resolve #802 conflict [skip ci]	2026-07-19 01:33:59 +00:00
jmiller	2cbf5b15ee	chore(ci): align deploy-rc.yml with main (Template-Go canonical) to resolve #802 conflict [skip ci]	2026-07-19 01:33:33 +00:00
jmiller	c64c6a5c51	chore(ci): align deploy-dev.yml with main (Template-Go canonical) to resolve #802 conflict [skip ci]	2026-07-19 01:33:12 +00:00
jmiller	b87606a904	Merge pull request 'fix(ci): drop concurrency from deploy workflows (auto-deploy like mokoai)' (#824) from feature/deploy-no-concurrency into dev	2026-07-19 00:34:33 +00:00
Moko Consulting	752fcbdc6b	fix(ci): drop concurrency block from deploy-{dev,rc,prod} — enable auto-deploy like mokoai ... MokoGIT's deploy-*.yml still carried a `concurrency:` block; MokoAI's does not. That block enlarges the marshaled workflow_payload past MySQL's 64KB BLOB limit, so InsertRun fails and the deploy run is silently dropped on push (#815) — which is exactly why mokoai auto-deploys to dev on push and mokogit doesn't. Remove it on all three tiers to match MokoAI / Template-Go's canonical version, so push-to- dev builds+deploys mokogit-dev automatically like mokoai-dev. Note: deploy-*.yml are Template-Go-synced and Template-Go already dropped these (Template-Go#22); MokoGIT was simply stale (never re-synced). This brings it current now; a future workflow-sync is a no-op. #816 (widen workflow_payload to MEDIUMBLOB) is the permanent engine-side fix. Authored-by: Moko Consulting	2026-07-18 19:32:51 -05:00
jmiller	1d334abc33	Merge pull request 'fix(actions): widen workflow_payload to MEDIUMBLOB — Actions creates no run (#815)' (#816) from feature/815-workflow-payload into dev	2026-07-19 00:05:18 +00:00
jmiller	c7507377c7	fix(actions): widen action_run_job.workflow_payload to MEDIUMBLOB (#815) ... Gitea Actions accepted workflow_dispatch (HTTP 204) but created no run: the async InsertRun failed with MySQL 1406 "Data too long for column 'workflow_payload'". ActionRunJob.WorkflowPayload was an untyped []byte -> plain BLOB (64 KiB) on MySQL/MariaDB. At run creation the whole SingleWorkflow is interpolated (every ${{ vars.* }} / git context) and marshaled into that column, so large single-job workflows (deploy-*.yml with big inline scripts + many vars) overflowed it and the run was silently dropped. - run_job.go: tag WorkflowPayload `xorm:"MEDIUMBLOB"` (16 MiB) so NEW installs get a wide column. - migration 371 (v372.go): ALTER existing action_run_job.workflow_payload BLOB -> MEDIUMBLOB on MySQL/MariaDB; no-op on Postgres/SQLite (unbounded). Permanently unblocks all deploy tiers regardless of the concurrency-block workaround. Fixes #815. Authored-by: Moko Consulting	2026-07-18 17:03:15 -05:00
jmiller	df395fc82b	Merge pull request 'chore(gitignore): ignore .gemini/ and local wiki/docs per ecosystem standard' (#813) from chore/ignore-gemini-wiki into dev	2026-07-18 21:19:54 +00:00
jmiller	9d141411bd	chore(gitignore): ignore .gemini/ and local wiki/docs per ecosystem standard ... Add the canonical Moko exclusions matching the Template repos: .gemini/ alongside .claude/, the AI client-instructions block, and the local wiki clone block (wiki/, docs/). Update CLAUDE.md never-commit rule if present. Authored-by: Moko Consulting	2026-07-18 14:58:29 -05:00
jmiller	e519677fcd	Merge pull request 'feat(setting): accept MOKOGIT__ env override prefix alongside GITEA__' (#808) from feature/mokogit-env-prefix into dev	2026-07-18 19:32:47 +00:00
jmiller	e0c6451fac	Merge pull request 'feat(theme): auto-import MokoOnyx template CSS + light/dark themes on push' (#807) from feature/mokoonyx-theme-sync into dev	2026-07-18 19:20:35 +00:00
jmiller	ada552aebf	feat(setting): accept MOKOGIT__ env override prefix alongside GITEA__ ... Step 1 of the coordinated GITEA__ -> MOKOGIT__ rebrand. The binary previously read config env overrides only under the GITEA__ prefix, so renaming the compose vars first would make Gitea silently ignore every override. Teach the binary to accept BOTH prefixes (MOKOGIT__ and GITEA__), including the __FILE suffix, so the compose vars can be migrated safely AFTER this binary is deployed to all tiers. - add EnvConfigKeyPrefixMokoGit ("MOKOGIT__") + envConfigKeyPrefixes list - CollectEnvConfigKeys / EnvironmentToConfig iterate both prefixes - test: MOKOGIT__ override applies (existing GITEA__ + __FILE behavior unchanged) Compose var rename (GITEA__* -> MOKOGIT__*) is a follow-up, gated on this being live everywhere. Upstream MIT header preserved. Authored-by: Moko Consulting	2026-07-18 14:18:42 -05:00
jmiller	5d2ec281b7	Merge pull request 'chore(rebrand): user-facing brand strings — MokoGIT (issue #801 phase 1)' (#805) from chore/rebrand-strings-p1 into dev	2026-07-18 18:56:04 +00:00
jmiller	2a99ded829	feat(theme): auto-import MokoOnyx template CSS + light/dark themes on push ... Add a MokoGIT-specific workflow that, on every push to dev/main (and on demand), vendors the MokoOnyx (mokoconsulting.tech Joomla template) CSS from the MokoConsulting/MokoOnyx repo into web_src/css/vendor/mokoonyx/, and extracts tokens-only files (re-scoped :root, Bootstrap component classes stripped) that are safe to @import into a Gitea theme without colliding with Fomantic UI. Commits back with [skip ci] only when something changed (no self-trigger loop). This is the "import" mechanism for token/variable parity with the site design. Wiring the tokens onto Gitea's --color-* vars is documented in the vendor README and left as a visually-tuned follow-up so an automated import can never silently recolor the UI. Workflow is MokoGIT-specific (only this repo has a web UI to theme), so it lives here and is not a Template-* concern. Authored-by: Moko Consulting	2026-07-18 13:53:33 -05:00
jmiller	ec65fac21f	Merge pull request 'feat(theme): swap auth backdrop to brand header-background.svg' (#806) from feat/header-bg-swap into dev	2026-07-18 18:35:07 +00:00
jmiller	e9b46f2e51	feat(theme): swap auth backdrop to brand header-background.svg ... Replace the interim mokoonyx-bg.svg (sourced from the marketing site) with the official brand asset from Shared Drives (Assets/branding/primary/background.svg), vendored as public/assets/img/header-background.svg, and point the auth-screen backdrop at it. Larger, higher-detail landscape artwork; same CSS treatment (cover/centered) and legible surface panel. Authored-by: Moko Consulting	2026-07-18 13:33:16 -05:00
jmiller	0f31f54e2b	Merge pull request 'feat(theme): MokoOnyx bg.svg as login/auth screen background' (#804) from feat/login-bg-mokoonyx into dev	2026-07-18 18:29:35 +00:00
jmiller	2e86f25977	chore(rebrand): user-facing Gitea->MokoGIT brand strings (issue #801 phase 1) ... Conservative, source-controlled brand-string pass — user-facing display text only. NO blanket gitea->mokogit (import paths, runtime paths, binary/command names, GITEA_* env, copyright/attribution all intentionally left untouched). - cmd/web.go: startup "Gitea version:" / "Starting|Restarting Gitea on PID" logs - modules/graceful/manager_unix.go: systemd sd_notify "Starting Gitea" status - modules/setting/setting.go: run-as-root Fatal/Warn messages - services/doctor/dbconsistency.go: doctor model-version Critical message - snap/snapcraft.yaml: summary text only (name:/command:/adopt-info: kept) - .github/ISSUE_TEMPLATE/bug-report.yaml: "Gitea Version" label + description (form field id: gitea-ver kept as a stable key) - .mokogit/issue_template.md: version checklist label - options/fileicon/material-icon-rules.json: rename stale ".mokogitea/workflows" keys -> ".mokogit/workflows" (values folder-gitea-workflows* kept; JSON-aware) - rename .mokogit/ISSUE_TEMPLATE/test-mokogitea.md -> test-mokogit.md Authored-by: Moko Consulting	2026-07-18 13:25:47 -05:00
jmiller	fefe9d157c	fix(theme): brand full auth family + cover WebAuthn surface (review #804) ... Per PR review: the "signin" body class is shared by the whole auth family (sign-in, sign-up, 2FA, OpenID, WebAuthn, change-password), so the backdrop applies to all of them by design — document that in the comment. Broaden the form-surface selector from `.ui.middle.page.grid > .column` to `.ui.page.grid > .column` so the WebAuthn prompt (whose grid has no `middle` class) also gets the legible surface instead of sitting on the raw pattern. Authored-by: Moko Consulting	2026-07-18 12:44:16 -05:00
jmiller	113e1bfb5e	refactor(theme): drop dead signup auth selectors (signup reuses signin class) ... The signup template renders the same class="page-content user signin" as signin, so the separate .signup selectors never matched. Signup is already covered by the .signin rules; remove the dead selectors and correct the comment. Authored-by: Moko Consulting	2026-07-18 12:32:19 -05:00
jmiller	90923a5ca1	feat(theme): use MokoOnyx bg.svg as the login/auth screen background ... Vendor the mokoconsulting.tech MokoOnyx background pattern and paint it behind the centered form on the signin/signup/link-account pages, matching the site design language. Implemented as a CSS-only change in the brand layer using :has() on <body> (no template markup), so it survives upstream Gitea merges. The auth form is lifted onto a clean, theme-token surface so it stays legible over the pattern in both light and dark themes. Asset self-hosted at public/assets/img/mokoonyx-bg.svg (served /assets/img/) for offline/distribution determinism — no dependency on the marketing site. Authored-by: Moko Consulting	2026-07-18 12:28:42 -05:00
jmiller	c71bb0c9af	Merge pull request 'fix(theme): repair broken theme + MokoOnyx surface separation' (#800) from jmiller/fix-theme-config-separation into dev	2026-07-17 15:42:38 +00:00
jmiller	dee280a98d	fix(theme): repair broken theme + add MokoOnyx surface separation ... The MokoGitea->MokoGIT branding rebrand deleted the gitea-* theme CSS and shipped only theme-mokogit-{auto,light,dark}.css, but two things were left pointing at the retired themes, producing an unstyled "all white" page with an invisible navbar theme toggle: 1. Users' saved `user.theme` still held gitea-* names, whose CSS now 404s. Add migration 370 (RemapGiteaThemesToMokogit) to rewrite each user's saved theme gitea-{auto,light,dark}(-colorblind) -> mokogit-* equivalent, preserving their light/dark/auto preference. Idempotent. 2. app.example.ini still documented DEFAULT_THEME = gitea-auto. Correct it to mokogit-auto so fresh installs start on a shipped theme. (The running servers' app.ini [ui] THEMES/DEFAULT_THEME are fixed operationally.) Also address the flat "all white / no separation" look by adding a MokoOnyx surface-separation scale to both themes (mokoconsulting.tech gray scale): - light: soft gray page (#f0f3f6) so white cards/boxes lift off it, gray-200 box headers, stronger gray-300 border definition. - dark: 3-step navy-tinted elevation (page #0b1017 -> box #121a24 -> header #17212e) cohesive with the #112855 brand nav, more visible panel edges. The auto theme @imports light/dark, so it inherits both automatically.	2026-07-17 01:58:48 -05:00
jmiller	102d1fe0a2	fix(cli): report 'mokogit version' instead of 'gitea version' ... The CLI app name (cmd/main.go app.Name) was still 'gitea', so `mokogit --version` and the USAGE/help printed 'gitea version X' and 'gitea doctor ...'. Rename it to 'mokogit' (lower-cased per the USAGE convention) and rebrand the two adjacent Gitea CLI strings (program description, --work-path usage). Verified: go build ./cmd/. Does NOT rename the executable file (still /app/gitea/gitea); that touches Dockerfile/systemd/deploy paths and is a separate, larger change.	2026-07-16 22:25:54 -05:00