wxiaoguang 236c645bf1 Refactor "Content" for file uploading (#25851) ... 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"` ``		2023-07-18 18:14:47 +00:00
..
avatar.go
blob.go
branch.go
collaborators.go
commits.go
file.go
fork.go
git_hook.go
git_ref.go
hook_test.go
hook.go
issue_attachment.go
issue_comment_attachment.go
issue_comment.go
issue_dependency.go
issue_label.go
issue_pin.go
issue_reaction.go
issue_stopwatch.go
issue_subscription.go
issue_tracked_time.go
issue.go
key.go
label.go
language.go
main_test.go
migrate.go
milestone.go
mirror.go
notes.go
patch.go
pull_review.go
pull.go
release_attachment.go
release_tags.go
release.go
repo_test.go
repo.go
star.go
status.go
subscriber.go
tag.go
teams.go
topic.go
transfer.go
tree.go
wiki.go