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

Open

jmiller wants to merge 1 commits from main into dev

pull from: main

merge into: :dev

:main

:fix/theme-config-separation

:dev

:feature/799-actions-a-concurrency-block-prevents-run

:feature/secret-scanning

:feature/727-org-level-branch-protection-is-stored-bu

:feature/725-enforce-dot-prefixed-repositories-are-al

:feature/723-feat-issue-and-pull-request-voting-upvot

:feature/722-cleanup-and-standardization-of-issue-tem

:feature/738-expand-openapi-spec-mcp-tooling-for-org-

:feature/747-add-a-dedicated-system-api-automation-bo

:feature/746-auto-add-the-actions-bot-to-the-ci-cd-te

:feature/745-org-default-teams-add-protected-option-b

:feature/744-feat-let-issue-templates-set-mokogitea-f

:worktree-agent-acb0cede999748165

:fix/rebrand-wiki-docs

:feature/749-release-notes-from-a-curated-release-not

:worktree-agent-a5b50d10bab2beaac

:feature/760-per-client-org-sweep-audit-client-mokosu

:feature/759-audit-client-extension-repos-for-stale-m

:feat/vnext

:fix/org-wiki

:rc

:rc/v1.26.1-moko.06.07.02

:rc/v1.26.1-moko.06.07.03

:rc/v1.26.1-moko.06.07.01

:rc/v1.26.1-moko.06.07

:rc/v1.26.1-moko.06.06.02

:rc/v1.26.1-moko.06.06.01

:rc/v1.26.1-moko.06.06

:rc/v1.26.1-moko.06.05.01

:rc/v1.26.1-moko.06.05

:rc/v1.26.1-moko.06.04

:rc/v1.26.1-moko.06.03

:rc/05.06.00

:rc/05.03.03

:rc/04.01.00

:rc/05.03.02

:rc/05.03.01

:rc/05.03.00

:rc/05.01.00

:rc/05.02.02

:rc/05.02.01

:rc/05.01.01

:rc/05.02.00

:rc/05.01.02

:rc/05.03.04

:rc/05.03.05

:rc/05.03.06

:rc/05.03.08

:rc/05.04.00

:rc/05.05.00

Conversation 0 Commits 1 Files Changed 1

+3 -3

jmiller commented 2026-07-16 13:40:44 +00:00

Owner

Copy Link

Copy Source

Cascade completed MOKOGITEA->MOKOGIT migration into dev.

Cascade completed MOKOGITEA->MOKOGIT migration into dev.

jmiller added 40 commits 2026-07-16 13:40:46 +00:00

Merge pull request 'release: rc -> main (stable) — admin-configurable metadata platform (#777)' (#786) from rc into main d1f3118a75

chore: sync auto-release.yml from Template-Go [skip ci] 2ae0fa7920

chore: sync deploy-dev.yml from Template-Go [skip ci] d931c71937

chore: sync deploy-prod.yml from Template-Go [skip ci] 4d15e6ccb8

chore: sync deploy-rc.yml from Template-Go [skip ci] 2c33645107

chore: sync auto-bump.yml from Template-Go [skip ci] bdf2646a04

chore: sync auto-release.yml from Template-Go [skip ci] 2a4841f6e7

chore: sync branch-cleanup.yml from Template-Go [skip ci] 28792802ec

chore: sync cascade-dev.yml from Template-Go [skip ci] 5dd416a4a2

chore: sync ci-generic.yml from Template-Go [skip ci] ef395e61a9

chore: sync ci-issue-reporter.yml from Template-Go [skip ci] 4b7f42f9d5

chore: sync cleanup.yml from Template-Go [skip ci] fb758f7227

chore: sync deploy-dev.yml from Template-Go [skip ci] 7fc04c8fb7

chore: sync deploy-prod.yml from Template-Go [skip ci] d7c91a001b

chore: sync deploy-rc.yml from Template-Go [skip ci] 067dc74894

chore: sync gitleaks.yml from Template-Go [skip ci] eaa3cdee7d

chore: sync issue-branch.yml from Template-Go [skip ci] 5db111c944

chore: sync notify.yml from Template-Go [skip ci] 08414bdb1a

chore: sync pr-check.yml from Template-Go [skip ci] 22c9699534

chore: sync pre-release.yml from Template-Go [skip ci] 5ad84d831f

chore: sync rc-revert.yml from Template-Go [skip ci] cdce9157a4

chore: sync repo-health.yml from Template-Go [skip ci] 18aeb85b2e

chore: sync standards-compliance.yml from Template-Go [skip ci] 24e24a5f75

chore: sync version-set.yml from Template-Go [skip ci] c3b4418216

fix(org-wiki): remove duplicated nav menu, fix intra-wiki links ... d73a40b734

- view.tmpl rendered both org/header (which already includes org/menu)
  and org/menu -> the org navigation bar showed twice. Drop the redundant
  org/menu include to match every other org page.
- Wiki content was rendered with a RepoFile context, so intra-wiki links
  pointed at /{owner}/{repo}/src/branch/main/PATH (repo file browser,
  missing .md -> 404). Rewrite rendered links (content/sidebar/footer) to
  /{owner}/-/wiki/PATH, which also hides the underlying wiki repo name.
- Reword empty-state hint to public / members-only wording.

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

fix(org-wiki): also rewrite absolute-form intra-wiki links ... 31c58d34f1

Match an optional https://host prefix so wiki links rendered as absolute
URLs (not just root-relative) are rewritten to the /-/wiki/ route too.
Covers nested pages like standards/Wiki-Structure.

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

fix(metadata): remove redundant Organization field from repo metadata page ... 3377e6895f

The Organization value is derived from the org profile (repo owner) and
was shown as a read-only field; it added no value, so remove it entirely
from the settings page. The DerivedOrgName model method stays (API still
derives org on read). See #771.

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

Merge pull request 'fix: prod hotfixes - metadata Organization field + org wiki nav/links' (#789) from rc into main 1741d5e863

fix(org): point profile/wiki repo lookup at renamed .mokogit repos ... 8a4b479129

The org .mokogitea/.mokogitea-private repos were renamed to .mokogit/
.mokogit-private, but the constants still pointed at the old names, so the
org profile + wiki lookup returned nil (empty wiki). Update the 4
RepoName* constants to match. Interim rebrand step.

Merge pull request 'fix(org): restore profile/wiki lookup to renamed .mokogit repos' (#790) from rc into main c8069f3d3f

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

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

chore: re-trigger dev deploy for MokoGIT rebrand ... 402f5d9412

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

Merge remote-tracking branch 'origin/main' into feature/rebrand-mokogit dda5e81c41

chore: drop orphaned .mokogit/workflows dupes from main merge ... 4885f3c123

The main->rebrand merge resurrected .mokogit/workflows/ (workflows live at
.mokogitea/workflows during the cutover, per WorkflowDirs). Remove the dupes.

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

Merge pull request 'feat: MokoGitea -> MokoGIT rebrand (validated on dev + rc)' (#793) from rc into main 1f73a14cb0

fix(repo): make system-repo name normalization case-sensitive ... e6898a876b

EqualFold matched the product name "MokoGIT" against reserved "mokogit",
normalizing it to ".MokoGIT" and colliding with the .mokogit org repo
(blocked renaming the fork to MokoGIT). Only exact lowercase bare names
should normalize.

Merge pull request 'fix(repo): case-sensitive system-repo name normalization' (#794) from rc into main 6dd0f1fb6d

fix: remove stale .mokogitea config dir (superseded by .mokogit) 7a71ebd0b1

Merge pull request 'fix: remove stale .mokogitea config dir (superseded by .mokogit)' (#795) from fix/migrate-mokogitea-to-mokogit into main 411bed0d05

jmiller added 1 commit 2026-07-16 18:23:17 +00:00

merge(main): promote dev to production ... dbcbff79ee

Session work: #798 WorkflowDirs (detect .mokogit/workflows, retire .mokogitea),
org internal-wiki merge, issue custom-status dropdown visibility fix, MokoOrgStandards
xx.xx.xx versioning + .vault deploy staging, and restored .mokogit/workflows from
Template-Go.

Conflict resolution: main had dropped .mokogit/workflows/* (4885f3c1 "drop orphaned
dupes"); kept dev's restored set. main's rebrand + prod hotfixes (#793/#794/#795,
.mokogitea config-dir removal) are preserved. CHANGELOG updated.

jmiller added 1 commit 2026-07-16 18:36:52 +00:00

chore: sync branch-cleanup.yml from Template-Go [skip ci] 8684ce0e3e

jmiller added 1 commit 2026-07-16 18:37:30 +00:00

chore: sync issue-branch.yml from Template-Go [skip ci] 3267fa42b1

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

fix(build): report the xx.xx.xx VERSION in Docker builds (not git describe) ... c5b15a8ea9

The Dockerfile bind-mounts .git for `make backend` ("required for version data"),
so the Makefile computed the binary version via `git describe` — the leaked upstream
Gitea version (e.g. 1.26.1+moko...-967-gHASH) — even though a VERSION file (01.00.00)
is committed. The Makefile's STORED_VERSION (VERSION file) takes precedence over
`git describe`, but .dockerignore excluded `/VERSION`, so the build never saw it.

Stop excluding VERSION from the Docker build context. STORED_VERSION=01.00.00 now
wins and the built binary reports the MokoOrgStandards xx.xx.xx version. (Upstream
excludes VERSION because it's normally a generated release-tarball artifact; MokoGIT
commits it intentionally as the version source.)

Verify after deploy: the footer and /api/v1/version report 01.00.00, not a git-describe
string. Completes the versioning adoption whose repo-side pieces (VERSION file,
update-checker default off) were already in place.

jmiller added 1 commit 2026-07-16 19:44:56 +00:00

feat: MokoGIT branding -- mokoconsulting.tech reskin, Font Awesome, toggle, a11y menu, PWA ... 81d065b9bb

Comprehensive MokoGIT theme/branding built from the authoritative mokoconsulting.tech
design tokens (MokoOnyx *.custom.css):

- Theme: replace gitea themes entirely with theme-mokogit-{light,dark,auto} (default
  mokogit-auto); brand tokens (primary #010156 / accent #3f8ff0, navy nav+footer #112855,
  semantic palette); mokogit-brand.css component reskin; runtime custom-stylesheet override
  hook (templates/custom/header.tmpl -> mokogit-custom.css, re-skin live with no rebuild).
- Font Awesome 7 Free 7.1.0: vendored unmodified (CSS headers intact + webfonts + verbatim
  LICENSE.txt), license-compliant for distribution/white-label (Icons CC BY 4.0, Fonts SIL
  OFL 1.1, Code MIT); attributed in THIRD-PARTY-NOTICES.md, README, and wiki.
- Light/dark toggle: navbar sun/moon control, server-persisted via the existing
  /user/settings/appearance/theme endpoint (anonymous falls back to localStorage).
- Accessibility menu: 6 options (text resize, color invert, high contrast, link highlight,
  readable font, pause animations); localStorage-persisted, applied on <html>, ARIA/keyboard.
- PWA: service worker (network-first navigation + cached offline fallback) + branded offline
  page + enhanced manifest (display standalone, navy theme_color, app shortcuts); manifest
  icon sourced from the site-admin branding icon if set, else the bundled MokoGIT logo.

Verified: `go build ./...` and `vite build` both green; only mokogit themes emit.

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

chore: sync auto-bump.yml from Template-Go [skip ci] c688c3d5c4

jmiller added 1 commit 2026-07-17 00:44:12 +00:00

chore: sync auto-release.yml from Template-Go [skip ci] ab4b89508d

jmiller added 1 commit 2026-07-17 00:44:23 +00:00

chore: sync branch-cleanup.yml from Template-Go [skip ci] 3cef1d542a

jmiller added 1 commit 2026-07-17 00:44:32 +00:00

chore: sync ci-generic.yml from Template-Go [skip ci] 98b7b00750

jmiller added 1 commit 2026-07-17 00:44:45 +00:00

chore: sync ci-issue-reporter.yml from Template-Go [skip ci] d362d7a997

jmiller added 1 commit 2026-07-17 00:44:54 +00:00

chore: sync cleanup.yml from Template-Go [skip ci] 74a865f671

jmiller added 1 commit 2026-07-17 00:45:09 +00:00

chore: sync issue-branch.yml from Template-Go [skip ci] 3d118bbc1f

jmiller added 1 commit 2026-07-17 00:45:19 +00:00

chore: sync notify.yml from Template-Go [skip ci] 2aef425eda

jmiller added 1 commit 2026-07-17 00:45:30 +00:00

chore: sync pr-check.yml from Template-Go [skip ci] dbb83fd76a

jmiller added 1 commit 2026-07-17 00:45:41 +00:00

chore: sync pre-release.yml from Template-Go [skip ci] cd026ad481

jmiller added 1 commit 2026-07-17 00:45:50 +00:00

chore: sync rc-revert.yml from Template-Go [skip ci] 46f1a88543

jmiller added 1 commit 2026-07-17 06:31:30 +00:00

fix(cli): report 'mokogit version' instead of 'gitea version' ... 7174fd0007

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.

Some required checks failed

Hide all checks

Universal: PR Check / Branch Policy (pull_request) Successful in 2s

Details

Universal: PR Check / Validate PR (pull_request) Successful in 10s

Details

Generic: Project CI / Lint & Validate (pull_request) Successful in 35s

Details

Generic: Standards Compliance / Secret Scanning (push) Failing after 11s

Details

Generic: Standards Compliance / License Header Validation (push) Successful in 9s

Details

Generic: Standards Compliance / Repository Structure Validation (push) Successful in 10s

Details

Generic: Standards Compliance / Coding Standards Check (push) Successful in 13s

Details

Universal: PR Check / Secret Scan (pull_request) Successful in 1m36s

Details

Deploy (Prod) / Build & Deploy to Prod (push) Failing after 1m27s

Details

Generic: Standards Compliance / Workflow Configuration Check (push) Failing after 11s

Details

Generic: Standards Compliance / Documentation Quality Check (push) Successful in 10s

Details

Generic: Standards Compliance / README Completeness Check (push) Failing after 10s

Details

Generic: Standards Compliance / Script Integrity Validation (push) Successful in 11s

Details

Generic: Standards Compliance / Line Length Check (push) Successful in 22s

Details

Generic: Standards Compliance / Version Consistency Check (push) Successful in 1m15s

Details

Generic: Standards Compliance / File Naming Standards (push) Successful in 10s

Details

Generic: Standards Compliance / Insecure Code Pattern Detection (push) Successful in 10s

Details

Generic: Standards Compliance / Git Repository Hygiene (push) Successful in 1m20s

Details

Generic: Standards Compliance / Dead Code Detection (push) Successful in 13s

Details

Generic: Standards Compliance / File Size Limits (push) Successful in 10s

Details

Generic: Standards Compliance / Code Complexity Analysis (push) Successful in 1m12s

Details

Generic: Standards Compliance / TODO/FIXME Tracking (push) Successful in 9s

Details

Generic: Standards Compliance / Code Duplication Detection (push) Successful in 2m25s

Details

Generic: Standards Compliance / Binary File Detection (push) Successful in 1m58s

Details

Generic: Standards Compliance / Broken Link Detection (push) Successful in 13s

Details

Generic: Standards Compliance / Dependency Vulnerability Scanning (push) Successful in 1m47s

Details

Generic: Standards Compliance / API Documentation Coverage (push) Successful in 10s

Details

Generic: Standards Compliance / Accessibility Check (push) Successful in 11s

Details

Generic: Standards Compliance / Performance Metrics (push) Successful in 11s

Details

Generic: Standards Compliance / Unused Dependencies Check (push) Successful in 1m17s

Details

Generic: Standards Compliance / Terraform Configuration Validation (push) Successful in 18s

Details

Generic: Standards Compliance / Enterprise Readiness Check (push) Successful in 1m4s

Details

Generic: Standards Compliance / Repository Health Check (push) Successful in 1m2s

Details

Generic: Project CI / Tests (pull_request) 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

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

Details

The changes on this branch are already on the target branch. This will be an empty commit.

You are not authorized to merge this pull request.

This pull request can be merged automatically.

This branch is out-of-date with the base branch

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

dependencies

Dependency updates

deploy-failure

Deployment failed

docker

Docker/container changes

documentation

Documentation changes

feature: wiki

Wiki system enhancements

good first issue

Good for newcomers

health-check

Repo health check result

help wanted

Extra attention needed

mokostandards

Related to MokoStandards framework

push-failure

Git push operation failed

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

tech-debt

Technical debt and TODO/FIXME items

upstream

upstream

Inherited from upstream Gitea

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) moko-deploy (Moko Deploy Bot)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGIT#796