mirror of https://github.com/go-gitea/gitea.git
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"` `` |
||
|---|---|---|
| .. | ||
| activity.go | ||
| activitypub.go | ||
| admin_user.go | ||
| attachment.go | ||
| commit_status.go | ||
| cron.go | ||
| doc.go | ||
| fork.go | ||
| git_blob.go | ||
| git_hook.go | ||
| hook.go | ||
| issue.go | ||
| issue_comment.go | ||
| issue_label.go | ||
| issue_milestone.go | ||
| issue_reaction.go | ||
| issue_stopwatch.go | ||
| issue_test.go | ||
| issue_tracked_time.go | ||
| lfs_lock.go | ||
| mirror.go | ||
| miscellaneous.go | ||
| nodeinfo.go | ||
| notifications.go | ||
| org.go | ||
| org_member.go | ||
| org_team.go | ||
| package.go | ||
| pull.go | ||
| pull_review.go | ||
| release.go | ||
| repo.go | ||
| repo_branch.go | ||
| repo_collaborator.go | ||
| repo_commit.go | ||
| repo_file.go | ||
| repo_key.go | ||
| repo_note.go | ||
| repo_refs.go | ||
| repo_tag.go | ||
| repo_topic.go | ||
| repo_tree.go | ||
| repo_watch.go | ||
| repo_wiki.go | ||
| settings.go | ||
| status.go | ||
| task.go | ||
| user.go | ||
| user_app.go | ||
| user_email.go | ||
| user_gpgkey.go | ||
| user_key.go | ||
| visible_type.go | ||