mirror of
https://github.com/go-gitea/gitea.git
synced 2024-12-14 20:34:07 +01:00
236c645bf1
Before: the concept "Content string" is used everywhere. It has some problems: 1. Sometimes it means "base64 encoded content", sometimes it means "raw binary content" 2. It doesn't work with large files, eg: uploading a 1G LFS file would make Gitea process OOM This PR does the refactoring: use "ContentReader" / "ContentBase64" instead of "Content" This PR is not breaking because the key in API JSON is still "content": `` ContentBase64 string `json:"content"` `` |
||
---|---|---|
.. | ||
archiver | ||
files | ||
adopt_test.go | ||
adopt.go | ||
avatar_test.go | ||
avatar.go | ||
branch.go | ||
cache.go | ||
check.go | ||
fork_test.go | ||
fork.go | ||
hooks.go | ||
lfs.go | ||
main_test.go | ||
push.go | ||
repository_test.go | ||
repository.go | ||
review_test.go | ||
review.go | ||
template.go | ||
transfer_test.go | ||
transfer.go |