gitea.git - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD: https://github.com/go-gitea/gitea

	Commit message (Collapse)	Author	Age	Files	Lines
*	Refactor cache-control (#33861)	wxiaoguang	2025-03-13	1	-4/+13
\| \| \|	And fix #21391
*	Move context from modules to services (#29440)	Lunny Xiao	2024-02-27	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Since `modules/context` has to depend on `models` and many other packages, it should be moved from `modules/context` to `services/context` according to design principles. There is no logic code change on this PR, only move packages. - Move `code.gitea.io/gitea/modules/context` to `code.gitea.io/gitea/services/context` - Move `code.gitea.io/gitea/modules/contexttest` to `code.gitea.io/gitea/services/contexttest` because of depending on context - Move `code.gitea.io/gitea/modules/upload` to `code.gitea.io/gitea/services/context/upload` because of depending on context
*	Less naked returns (#25713)	6543	2023-07-07	1	-2/+2
\| \| \| \| \|	just a step towards #25655 and some related refactoring
*	Decouple the different contexts from each other (#24786)	wxiaoguang	2023-05-21	1	-4/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Replace #16455 Close #21803 Mixing different Gitea contexts together causes some problems: 1. Unable to respond proper content when error occurs, eg: Web should respond HTML while API should respond JSON 2. Unclear dependency, eg: it's unclear when Context is used in APIContext, which fields should be initialized, which methods are necessary. To make things clear, this PR introduces a Base context, it only provides basic Req/Resp/Data features. This PR mainly moves code. There are still many legacy problems and TODOs in code, leave unrelated changes to future PRs.
*	Make repository response support HTTP range request (#24592)	wxiaoguang	2023-05-09	1	-0/+43
	Replace #20480 Replace #18448 Close #16414