MokoConsulting/MokoGitea
1
0
Fork 0
Code Issues 86 Pull Requests 3 Actions Packages Projects Releases 27 Wiki Activity
20,994 Commits 46 Branches 277 Tags
dev
Commit Graph

7 Commits

Author SHA1 Message Date
Jonathan Miller c572fcfe04 chore(core): rename Go module from code.gitea.io/gitea to MokoGitea namespace
PR RC Release / Build RC Release (pull_request) Failing after 0s
Details
Branch Policy Check / Verify merge target (pull_request) Failing after 0s
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
Copilot 2671b997f2 Refactor integration test DecodeJSON calls to use generic return value (#37432) 
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: wxiaoguang <2114189+wxiaoguang@users.noreply.github.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
 2026-04-26 14:57:07 +00:00
wxiaoguang 8cc8150922 Use full-file highlighting for diff sections (#36561) 
* Fix #35252
* Fix #35999
* Improve diff rendering, don't add unnecessary "added"/"removed" tags for a full-line change
* Also fix a "space trimming" bug in #36539 and add tests
* Use chroma "SQL" lexer instead of "MySQL" to workaround a bug (35999)
 2026-02-10 03:29:28 +00:00
wxiaoguang e47bba046c Fix test code (#33829) 
Do not use onGiteaRun if there is no git operation
 2025-03-10 21:45:42 +00:00
Dustin Firebaugh 3f1f808b9e Full-file syntax highlighting for diff pages (#33766) 
Fix #33358, fix #21970

This adds a step in the `GitDiffForRender` that does syntax highlighting for the
entire file and then only references lines from that syntax highlighted
code. This allows things like multi-line comments to be syntax
highlighted correctly.

---------

Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
 2025-03-09 12:51:58 +08:00
Lunny Xiao fbe6d9dc6b Use batch database operations instead of one by one to optimze api pulls (#32680) 
Resolve #31492

The response time for the Pull Requests API has improved significantly,
dropping from over `2000ms` to about `350ms` on my local machine. It's
about `6` times faster.

A key area for further optimization lies in batch-fetching data for
`apiPullRequest.ChangedFiles, apiPullRequest.Additions, and
apiPullRequest.Deletions`.

Tests `TestAPIViewPulls` does exist and new tests added.

- This PR also fixes some bugs in `GetDiff` functions.
- This PR also fixes data inconsistent in test data. For a pull request,
the head branch's reference should be equal to the reference in
`pull/xxx/head`.
 2024-12-11 05:15:06 +08:00
Zettat123 f4b8f6fc40 Fix the logic of finding the latest pull review commit ID (#32139) 
Fix #31423
 2024-10-01 01:58:55 +00:00