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
*	Make sure git version&feature are always prepared (#30877)	wxiaoguang	2024-05-06	1	-1/+1
\| \| \|	Otherwise there would be more similar issues like #29287
*	Fix incorrect object id hash function (#30708)	wxiaoguang	2024-04-26	1	-3/+0
\| \| \| \| \| \| \| \| \| \| \| \| \|	Great thanks to @oliverpool for figuring out the problem and proposing a fix. Regression of #28138 Incorrect hash causes the user's LFS files get all deleted when running `doctor fix all` (by the way, remove unused/non-standard comments) Co-authored-by: Giteabot <teabot@gitea.io>
*	Add support for sha256 repositories (#23894)	Adam Majer	2024-01-19	1	-0/+16
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Currently only SHA1 repositories are supported by Gitea. This adds support for alternate SHA256 with the additional aim of easier support for additional hash types in the future. Fixes: #13794 Limited by: https://github.com/go-git/go-git/issues/899 Depend on: #28138 <img width="776" alt="图片" src="https://github.com/go-gitea/gitea/assets/81045/5448c9a7-608e-4341-a149-5dd0069c9447"> --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: 6543 <6543@obermui.de>
*	Improve ObjectFormat interface (#28496)	Lunny Xiao	2023-12-19	1	-66/+22
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The 4 functions are duplicated, especially as interface methods. I think we just need to keep `MustID` the only one and remove other 3. ``` MustID(b []byte) ObjectID MustIDFromString(s string) ObjectID NewID(b []byte) (ObjectID, error) NewIDFromString(s string) (ObjectID, error) ``` Introduced the new interfrace method `ComputeHash` which will replace the interface `HasherInterface`. Now we don't need to keep two interfaces. Reintroduced `git.NewIDFromString` and `git.MustIDFromString`. The new function will detect the hash length to decide which objectformat of it. If it's 40, then it's SHA1. If it's 64, then it's SHA256. This will be right if the commitID is a full one. So the parameter should be always a full commit id. @AdamMajer Please review.
*	Adjust object format interface (#28469)	Lunny Xiao	2023-12-17	1	-20/+13
\| \| \| \| \| \| \|	- Remove `ObjectFormatID` - Remove function `ObjectFormatFromID`. - Use `Sha1ObjectFormat` directly but not a pointer because it's an empty struct. - Store `ObjectFormatName` in `repository` struct
*	Only use SHA256 feature when git >= 2.42 (#28466)	wxiaoguang	2023-12-14	1	-5/+3
\| \| \|	And fix some comments
*	Abstract hash function usage (#28138)	Adam Majer	2023-12-13	1	-0/+143
	Refactor Hash interfaces and centralize hash function. This will allow easier introduction of different hash function later on. This forms the "no-op" part of the SHA256 enablement patch.