Nate Levesque f891172ef4 handle repository.size column being NULL in migration v263 (#28336) ... This resolves a problem I encountered while updating gitea from 1.20.4 to 1.21. For some reason (correct or otherwise) there are some values in `repository.size` that are NULL in my gitea database which cause this migration to fail due to the NOT NULL constraints. Log snippet (excuse the escape characters) ``` ESC[36mgitea |ESC[0m 2023-12-04T03:52:28.573122395Z 2023/12/04 03:52:28 ...ations/migrations.go:641:Migrate() [I] Migration[263]: Add git_size and lfs_size columns to repository table ESC[36mgitea |ESC[0m 2023-12-04T03:52:28.608705544Z 2023/12/04 03:52:28 routers/common/db.go:36:InitDBEngine() [E] ORM engine initialization attempt #3/10 failed. Error: migrate: migration[263]: Add git_size and lfs_size columns to repository table failed: NOT NULL constraint failed: repository.git_size ``` I assume this should be reasonably safe since `repository.git_size` has a default value of 0 but I don't know if that value being 0 in the odd situation where `repository.size == NULL` has any problematic consequences.		2023-12-05 14:31:13 +00:00
..
main_test.go
v260.go
v261.go
v262.go
v263.go	handle repository.size column being NULL in migration v263 (#28336)	2023-12-05 14:31:13 +00:00
v264.go
v265.go
v266.go	Restore warning commit status (#27504)	2023-10-08 22:16:06 +00:00
v267.go
v268.go
v269.go
v270.go
v271.go
v272.go
v273.go	chore(actions): support cron schedule task (#26655)	2023-08-24 03:06:51 +00:00
v274.go	Artifacts retention and auto clean up (#26131)	2023-09-06 07:41:06 +00:00
v275.go	Add a new column schedule_id for action_run to track (#26975)	2023-09-08 23:01:19 +08:00
v276.go	Fix wrong xorm get usage on migration (#27111)	2023-09-18 22:59:19 +03:00
v277.go	Add index to issue_user.issue_id (#27154)	2023-09-21 01:30:48 +00:00
v278.go	Add Index to comment.dependent_issue_id (#27325)	2023-09-28 22:58:35 +02:00
v279.go	Add Index to action.user_id (#27403)	2023-10-03 21:41:25 -04:00