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
*	enforce nolint scope (#34851)	TheFox0x7	2025-06-27	9	-9/+9
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	enable nolintlint scope requirement add comments to new directives so it's more obvious why they are in place --- I can also toggle the mandatory comments on if that's something of interest. --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> Co-authored-by: Giteabot <teabot@gitea.io>
*	Enforce two-factor auth (2FA: TOTP or WebAuthn) (#34187)	wxiaoguang	2025-04-28	1	-0/+57
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Fix #880 Design: 1. A global setting `security.TWO_FACTOR_AUTH`. * To support org-level config, we need to introduce a better "owner setting" system first (in the future) 2. A user without 2FA can login and may explore, but can NOT read or write to any repositories via API/web. 3. Keep things as simple as possible. * This option only aggressively suggest users to enable their 2FA at the moment, it does NOT guarantee that users must have 2FA before all other operations, it should be good enough for real world use cases. * Some details and tests could be improved in the future since this change only adds a check and seems won't affect too much. --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
*	Explicitly not update indexes when sync database schemas (#34281)	Lunny Xiao	2025-04-26	5	-7/+25
\| \| \| \| \| \| \|	Fix #34275 --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
*	feat: Add sorting by exclusive labels (issue priority) (#33206)	Thomas E Lackey	2025-04-10	1	-0/+16
\| \| \| \| \| \| \| \| \| \| \| \| \|	Fix #2616 This PR adds a new sort option for exclusive labels. For exclusive labels, a new property is exposed called "order", while in the UI options are populated automatically in the `Sort` column (see screenshot below) for each exclusive label scope. --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
*	Add anonymous access support for private repositories (backend) (#33257)	wxiaoguang	2025-03-28	1	-0/+17
\| \| \| \| \| \| \| \| \| \| \|	Follow #33127 This PR add backend logic and test for "anonymous access", it shares the same logic as "everyone access", so not too much change. By the way, split `SettingsPost` into small functions to make it easier to make frontend-related changes in the future. Next PR will add frontend support for "anonymous access"
*	Optimize heatmap query (#33853)	Lunny Xiao	2025-03-20	1	-0/+56
\| \| \| \| \| \| \| \| \| \| \|	When there are over 5M records on `action` table, the heatmap on dashboard is very slow as below SQL. ``` database duration=1.8881s db.sql="SELECT created_unix DIV 900 * 900 AS timestamp, count(user_id) as contributions FROM `action` WHERE user_id=? AND act_user_id=? AND (created_unix > ?) GROUP BY timestamp ORDER BY timestamp" ``` This PR add a new index for `action` table with columns `user_id`, `act_user_id` and `created_unix` so that this query will become about 6 times faster than before.
*	Added Description Field for Secrets and Variables (#33526)	John Smith	2025-03-17	1	-0/+20
\| \| \| \| \| \| \|	Fixes #33484 --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
*	Feature: Ephemeral action runners (#33570)	ChristopherHX	2025-03-14	1	-0/+16
\| \| \| \| \| \| \| \|	* This includes a runner mock test for hardend PickTask behavior like described in my proposal * Runner register ephemeral flag introduced in https://gitea.com/gitea/act_runner/pulls/649 Closes #32461
*	Add migrations and doctor fixes (#33556)	Lunny Xiao	2025-03-02	1	-0/+19
\| \| \|	Fix #33535
*	Move issue pin to an standalone table for querying performance (#33452)	Lunny Xiao	2025-02-17	1	-0/+31
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Noticed a SQL in gitea.com has a bigger load. It seems both `is_pull` and `pin_order` are not indexed columns in the database. ```SQL SELECT `id`, `repo_id`, `index`, `poster_id`, `original_author`, `original_author_id`, `name`, `content`, `content_version`, `milestone_id`, `priority`, `is_closed`, `is_pull`, `num_comments`, `ref`, `pin_order`, `deadline_unix`, `created_unix`, `updated_unix`, `closed_unix`, `is_locked`, `time_estimate` FROM `issue` WHERE (repo_id =?) AND (is_pull = 0) AND (pin_order > 0) ORDER BY pin_order ``` I came across a comment https://github.com/go-gitea/gitea/pull/24406#issuecomment-1527747296 from @delvh , which presents a more reasonable approach. Based on this, this PR will migrate all issue and pull request pin data from the `issue` table to the `issue_pin` table. This change benefits larger Gitea instances by improving scalability and performance. --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
*	Automerge supports deleting branch automatically after merging (#32343)	Lunny Xiao	2025-01-10	1	-0/+21
	Resolve #32341 ~Depends on #27151~ - [x] It will display a checkbox of deleting the head branch on the pull request view page when starting an auto-merge task. - [x] Add permission check before deleting the branch - [x] Add delete branch comment for those closing pull requests because of head branch or base branch was deleted. - [x] Merge `RetargetChildrenOnMerge` and `AddDeletePRBranchComment` into `service.DeleteBranch`.