oliverpool 8030614386 fix: release page for empty or non-existing target (#24470) ... Fixes #24145 To solve the bug, I added a "computed" `TargetBehind` field to the `Release` model, which indicates the target branch of a release. This is particularly useful if the target branch was deleted in the meantime (or is empty). I also did a micro-optimization in `calReleaseNumCommitsBehind`. Instead of checking that a branch exists and then call `GetBranchCommit`, I immediately call `GetBranchCommit` and handle the `git.ErrNotExist` error. This optimization is covered by the added unit test.		2023-05-10 11:43:55 +08:00
..
admin	Rewrite queue (#24505)	2023-05-08 19:49:59 +08:00
api/packages/pypi
base	Improve template system and panic recovery (#24461)	2023-05-04 14:36:34 +08:00
code
custom
devtest
explore	Change join_on translation to joined_on and include placeholder for the date (#24550)	2023-05-06 18:10:30 +08:00
mail
org	Revert "Prevent a user with a different email from accepting the team invite" (#24531)	2023-05-05 15:59:12 +08:00
package	Add RPM registry (#23380)	2023-05-05 20:33:37 +00:00
projects	Add permission check for moving issue action in project view page (#24589)	2023-05-09 00:50:16 -04:00
repo	fix: release page for empty or non-existing target (#24470)	2023-05-10 11:43:55 +08:00
shared	Change add_on translation to added_on and include placeholder for the date (#24562)	2023-05-06 21:11:27 +08:00
status	Improve template system and panic recovery (#24461)	2023-05-04 14:36:34 +08:00
swagger	Filter get single commit (#24613)	2023-05-10 09:34:07 +08:00
user	Add Gitea Profile Readmes (#23260)	2023-05-09 05:57:24 +00:00
home.tmpl
install.tmpl
post-install.tmpl