MokoConsulting/MokoGIT
1
0
Fork 0
Code Issues 156 Pull Requests 4 Releases 96 Wiki Activity

chore(rebrand): user-facing brand strings — MokoGIT (issue #801 phase 1) #805

Merged
jmiller merged 1 commits from chore/rebrand-strings-p1 into dev 2026-07-18 18:56:18 +00:00
Conversation 0 Commits 1 Files Changed 9
+13 -13
jmiller commented 2026-07-18 18:26:21 +00:00
Owner
Copy Link
Copy Source

Phase 1 of the Gitea → MokoGIT rebrand (issue #801): user-facing display strings only, source-controlled, low risk.

Deliberately NOT changed (per #801): import paths, runtime/data paths, binary & CLI command names (gitea web), GITEA_*/GITEA__ env prefixes, copyright/MIT-attribution headers, form field IDs, snap package name:/command:. No blanket gitea→mokogit.

Changes

  • cmd/web.go — startup logs: "Gitea version:", "Starting/Restarting Gitea on PID"
  • modules/graceful/manager_unix.go — systemd sd_notify status "Starting Gitea"
  • 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
  • .github/ISSUE_TEMPLATE/bug-report.yaml — "Gitea Version" label + description (kept id: gitea-ver)
  • .mokogit/issue_template.md — version checklist label
  • options/fileicon/material-icon-rules.json — renamed stale .mokogitea/workflows KEYS → .mokogit/workflows (JSON-aware; kept folder-gitea-workflows* sprite values)
  • renamed .mokogit/ISSUE_TEMPLATE/test-mokogitea.md → test-mokogit.md

All changes are string literals inside existing calls — no logic/compile impact. go build ./... + vite build run in CI.

Testing checklist (pre-merge — do not close on implementation alone)

  • CI go build ./... green
  • Startup logs show "MokoGIT version" / "Starting MokoGIT on PID"
  • doctor model-version message reads MokoGIT
  • material-icon-rules.json parses; .mokogit/workflows folder icon renders
  • bug-report issue form shows "MokoGIT Version"

Refs #801 (phase 1 of 5).

Phase 1 of the Gitea → MokoGIT rebrand (issue #801): **user-facing display strings only**, source-controlled, low risk. **Deliberately NOT changed** (per #801): import paths, runtime/data paths, binary & CLI command names (`gitea web`), `GITEA_*`/`GITEA__` env prefixes, copyright/MIT-attribution headers, form field IDs, snap package `name:`/`command:`. No blanket `gitea`→`mokogit`. ### Changes - `cmd/web.go` — startup logs: "Gitea version:", "Starting/Restarting Gitea on PID" - `modules/graceful/manager_unix.go` — systemd `sd_notify` status "Starting Gitea" - `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 - `.github/ISSUE_TEMPLATE/bug-report.yaml` — "Gitea Version" label + description (kept `id: gitea-ver`) - `.mokogit/issue_template.md` — version checklist label - `options/fileicon/material-icon-rules.json` — renamed stale `.mokogitea/workflows` KEYS → `.mokogit/workflows` (JSON-aware; kept `folder-gitea-workflows*` sprite values) - renamed `.mokogit/ISSUE_TEMPLATE/test-mokogitea.md` → `test-mokogit.md` All changes are string literals inside existing calls — no logic/compile impact. `go build ./...` + `vite build` run in CI. ### Testing checklist (pre-merge — do not close on implementation alone) - [ ] CI `go build ./...` green - [ ] Startup logs show "MokoGIT version" / "Starting MokoGIT on PID" - [ ] `doctor` model-version message reads MokoGIT - [ ] material-icon-rules.json parses; `.mokogit/workflows` folder icon renders - [ ] bug-report issue form shows "MokoGIT Version" Refs #801 (phase 1 of 5).
jmiller added 1 commit 2026-07-18 18:26:25 +00:00
chore(rebrand): user-facing Gitea->MokoGIT brand strings (issue #801 phase 1)
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 1m23s
Details
Universal: PR Check / Branch Policy (pull_request) Successful in 2s
Details
Generic: Project CI / Lint & Validate (pull_request) Successful in 42s
Details
Universal: PR Check / Validate PR (pull_request) Successful in 12s
Details
Universal: PR Check / Secret Scan (pull_request) Successful in 1m22s
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
RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped
Details
Branch Cleanup / Delete merged branch (pull_request) Successful in 2s
Details
2e86f25977 
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
jmiller merged commit 5d2ec281b7 into dev 2026-07-18 18:56:18 +00:00
jmiller deleted branch chore/rebrand-strings-p1 2026-07-18 18:56:20 +00:00
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
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/MokoGIT#805
Delete Branch "chore/rebrand-strings-p1"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?