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
..
e2e	disable gravatar in test (#32529)	2024-11-21 04:30:48 +00:00
fuzz	Refactor markup render system (#32645)	2024-11-26 16:46:02 +00:00
gitea-lfs-meta
gitea-repositories-meta	Use batch database operations instead of one by one to optimze api pulls (#32680)	2024-12-11 05:15:06 +08:00
integration	Use batch database operations instead of one by one to optimze api pulls (#32680)	2024-12-11 05:15:06 +08:00
testdata/data
mssql.ini.tmpl
mysql.ini.tmpl
pgsql.ini.tmpl
sqlite.ini.tmpl
test_utils.go	Improve testing and try to fix MySQL hanging (#32515)	2024-11-15 23:45:07 +08:00