MokoConsulting/MokoGitea-Fork
1
0
Fork 0
Code Issues 167 Pull Requests Releases 96 Wiki Activity
21,857 Commits 47 Branches 347 Tags
dev
Commit Graph

6 Commits

Author SHA1 Message Date
Jonathan Miller 9a5720e8ad chore: rename Go module from git. to code.mokoconsulting.tech (#336)
Branch Policy Check / Verify merge target (pull_request) Has been cancelled
Details
Universal: PR Check / Branch Policy (pull_request) Has been cancelled
Details
PR RC Release / Build RC Release (pull_request) Has been cancelled
Details
Universal: PR Check / Validate PR (pull_request) Has been cancelled
Details
Branch Cleanup / Delete merged branch (pull_request) Has been cancelled
Details
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Details 
Full namespace migration: update the Go module path and all import
statements from git.mokoconsulting.tech to code.mokoconsulting.tech.
Also updates all URL references in templates, workflows, configs,
tests, and documentation.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-05-31 10:28:25 -05:00
Jonathan Miller c572fcfe04 chore(core): rename Go module from code.gitea.io/gitea to MokoGitea namespace
Branch Policy Check / Verify merge target (pull_request) Has been cancelled
Details
PR RC Release / Build RC Release (pull_request) Has been cancelled
Details 
Rename the Go module path from code.gitea.io/gitea to
git.mokoconsulting.tech/MokoConsulting/MokoGitea across the entire
codebase.

Scope:
- go.mod module declaration
- 2,235 Go source files (import paths)
- Dockerfile WORKDIR and COPY paths
- Swagger API templates
- golangci.yml linter config

External dependencies (code.gitea.io/gitea-vet, code.gitea.io/sdk/gitea,
gitea.com/gitea/act, etc.) are intentionally NOT renamed — they are
separate upstream modules.

Closes #132

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
 2026-05-25 00:22:38 -05:00
KN4CK3R 27d4c11ec3 Fix joins in db.Find(AndCount) (#28978) 2024-01-30 02:37:24 +00:00
Lunny Xiao 70c4aad8e1 Move more functions to db.Find (#28419) 
Following #28220

This PR move more functions to use `db.Find`.

---------

Co-authored-by: delvh <dev.lh@web.de>
 2024-01-15 02:19:25 +00:00
Lunny Xiao df1e7d0067 Use db.Find instead of writing methods for every object (#28084) 
For those simple objects, it's unnecessary to write the find and count
methods again and again.
 2023-11-24 03:49:41 +00:00
Lunny Xiao a8c4f8cebc Fix db.Find bug (#23115) 
Caused by #20821 

Fix #23110
 2023-02-24 21:17:09 +08:00