MokoGitea-Fork

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
Giteabot	6e0236d433	fix(security): enforce wiki git writes and LFS token access at request time (#37695 ) (#37714 ) Backport #37695 by @lunny This PR fixes two permission-checking gaps in Git and LFS request handling. ## What it changes - keep wiki Git HTTP pushes on the normal write-permission path, even when proc-receive support is enabled - revalidate LFS bearer token requests against the current user state and current repository permissions before allowing access - add regression coverage for unauthorized wiki HTTP pushes - add LFS tests for blocked users, revoked repository access, read-only upload attempts, and valid write access ## Why - wiki repositories should not inherit the relaxed refs/for handling used for normal code repositories - LFS authorization tokens should not remain usable after a user is disabled or loses repository access --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>	2026-05-24 03:35:22 -05:00
wxiaoguang	b2ee5be52e	Refactor legacy code (#35708 ) And by the way, remove the legacy TODO, split large functions into small ones, and add more tests	2025-10-20 11:43:08 -07:00

4 Commits