MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 104 Pull Requests 1 Actions Packages Projects Releases 1 Wiki Activity

chore: replace upstream Gitea references with MokoGitea equivalents #76

New Issue
Closed
opened 2026-05-13 00:13:30 +00:00 by jmiller · 1 comment
jmiller commented 2026-05-13 00:13:30 +00:00
Owner
Copy Link
Copy Source

Summary

Replace all hardcoded references to upstream Gitea infrastructure (docs.gitea.com, about.gitea.com, blog.gitea.com) with MokoGitea equivalents as part of the fork separation.

Affected Areas

High Priority (User-Facing)

  • Footer "Powered by" link (templates/base/footer_content.tmpl) � about.gitea.com ? MokoGitea
  • Navbar help links (templates/base/head_navbar.tmpl) � docs.gitea.com ? MokoGitea docs
  • Admin dashboard update banner (already removed)

Medium Priority (Functional)

  • Webhook description links in routers/web/admin/hooks.go and routers/web/repo/setting/webhook.go
  • Broken git hook warning in routers/web/repo/view_home.go
  • Actions "no workflows" template
  • Repo settings templates (options, tags)
  • Auth provider docs link
  • Runner list template

Lower Priority (Package Registry Docs)

  • ~25 package registry templates linking to docs.gitea.com/usage/packages/*

Consider

  • Make the documentation base URL configurable via app.ini setting rather than hardcoding a new URL
  • Create a setting.DocsURL that all templates reference

Not Changed

  • code.gitea.io/gitea Go import paths � these are module paths, not infrastructure references
  • Test files with example URLs
  • Locale/translation files (separate effort)

Authored-by: Moko Consulting

## Summary Replace all hardcoded references to upstream Gitea infrastructure (`docs.gitea.com`, `about.gitea.com`, `blog.gitea.com`) with MokoGitea equivalents as part of the fork separation. ## Affected Areas ### High Priority (User-Facing) - [ ] Footer "Powered by" link (`templates/base/footer_content.tmpl`) � `about.gitea.com` ? MokoGitea - [ ] Navbar help links (`templates/base/head_navbar.tmpl`) � `docs.gitea.com` ? MokoGitea docs - [ ] Admin dashboard update banner (already removed) ### Medium Priority (Functional) - [ ] Webhook description links in `routers/web/admin/hooks.go` and `routers/web/repo/setting/webhook.go` - [ ] Broken git hook warning in `routers/web/repo/view_home.go` - [ ] Actions "no workflows" template - [ ] Repo settings templates (options, tags) - [ ] Auth provider docs link - [ ] Runner list template ### Lower Priority (Package Registry Docs) - [ ] ~25 package registry templates linking to `docs.gitea.com/usage/packages/*` ### Consider - Make the documentation base URL configurable via `app.ini` setting rather than hardcoding a new URL - Create a `setting.DocsURL` that all templates reference ## Not Changed - `code.gitea.io/gitea` Go import paths � these are module paths, not infrastructure references - Test files with example URLs - Locale/translation files (separate effort) --- *Authored-by: Moko Consulting*
jmiller commented 2026-05-20 01:44:55 +00:00
Author
Owner
Copy Link
Copy Source

Completed

All upstream Gitea references replaced with MokoGitea equivalents.

  • .mokogitea dot-folder support (workflows, issue/PR templates, repo templates, icons)
  • Moko Consulting branding on all pages
  • Container renamed to mokogitea
  • Upstream GitHub links stripped from workflows
  • Import paths migrated

Running in production: v1.26.1+244

Authored-by: Claude Opus 4.6 (1M context)

## Completed All upstream Gitea references replaced with MokoGitea equivalents. - .mokogitea dot-folder support (workflows, issue/PR templates, repo templates, icons) - Moko Consulting branding on all pages - Container renamed to mokogitea - Upstream GitHub links stripped from workflows - Import paths migrated Running in production: v1.26.1+244 *Authored-by: Claude Opus 4.6 (1M context)*
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 mokostandards
Related to MokoStandards framework
 priority: critical
Must fix immediately
 priority: high
Important, fix soon
 priority: low
Nice to have
 priority: medium
Normal priority
 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
 status: blocked
Blocked by dependency or decision
 status: in-progress
Actively being worked on
 status: needs-review
Awaiting code review
 status: on-hold
Paused intentionally
 status: wontfix
Will not be addressed
 sync-failure
Sync or mirror failed
 type: bug
Something isn't working
 type: chore
Maintenance, dependencies, cleanup
 type: enhancement
Improvement to existing feature
 type: feature
New functionality
 type: refactor
Code restructuring without behavior change
 type: version
Version bump or release
 work-in-progress
Draft or incomplete work
bug
Something is not working
 chore
Maintenance and housekeeping
 documentation
Documentation improvements
 enhancement
Improvement to existing functionality
 feature
New feature or request
 priority: critical
Must fix immediately
 priority: high
Should fix soon
 priority: low
Nice to have
 priority: medium
Fix when convenient
 refactor
Code restructuring without behavior change
 roadmap
Planned feature or enhancement tracked on the roadmap
 scope: client
Client-specific work
 scope: dolibarr
Dolibarr modules and customizations
 scope: infrastructure
Server, CI, backups, monitoring
 scope: joomla
Joomla templates and extensions
 scope: waas
MokoWaaS platform
 security
Security vulnerability or hardening
 status: blocked
Waiting on external dependency
 status: duplicate
Duplicate of another issue
 status: in-progress
Being worked on
 status: needs-review
Ready for review
 status: wontfix
Will not be addressed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
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/MokoGitea#76
Delete Branch "%!s()"

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?