Lunny Xiao 69ebc2f7d8 Use repo object format name instead of detecting from git repository (#29702) ... It's unnecessary to detect the repository object format from git repository. Just use the repository's object format name. (cherry picked from commit 3c6fc25a77c37d50686caa495d27a31dcef7f75f) Conflicts: services/pull/pull.go		2024-03-20 08:46:28 +01:00
..
check.go	Use the database object format name but not read from git repoisitory everytime and fix possible migration wrong objectformat when migrating a sha256 repository (#29294)	2024-02-26 22:30:26 +01:00
check_test.go
comment.go
commit_status.go	Fix commit_status problem when testing (#29672)	2024-03-11 23:36:59 +07:00
commit_status_test.go	Fixing the issue when status check per rule matches multiple actions (#29631)	2024-03-11 23:36:59 +07:00
edits.go
lfs.go
main_test.go
merge.go	Use the database object format name but not read from git repoisitory everytime and fix possible migration wrong objectformat when migrating a sha256 repository (#29294)	2024-02-26 22:30:26 +01:00
merge_ff_only.go	Add merge style fast-forward-only (#28954)	2024-02-14 17:19:19 +01:00
merge_merge.go	Add merge style fast-forward-only (#28954)	2024-02-14 17:19:19 +01:00
merge_prepare.go
merge_rebase.go
merge_squash.go
merge_test.go
patch.go
patch_unmerged.go
pull.go	Use repo object format name instead of detecting from git repository (#29702)	2024-03-20 08:46:28 +01:00
pull_test.go
review.go	remove util.OptionalBool and related functions (#29513)	2024-03-06 12:10:46 +08:00
temp_repo.go
update.go	[GITEA] avoid superfluous synchronized pull_request run when opening a PR (#2236)	2024-02-05 16:57:58 +01:00
update_rebase.go