gitea

Commit Graph

Author	SHA1	Message	Date
TheFox0x7	33e8e82c4b	Enable tenv and testifylint rules (#32852 ) Enables tenv and testifylint linters closes: https://github.com/go-gitea/gitea/issues/32842	2 months ago
Lunny Xiao	534917d576	Don't remove all mirror repository's releases when mirroring (#28817 ) Fix #22066 # Purpose This PR fix the releases will be deleted when mirror repository sync the tags. # The problem In the previous implementation of #19125. All releases record in databases of one mirror repository will be deleted before sync. Ref: https://github.com/go-gitea/gitea/pull/19125/files#diff-2aa04998a791c30e5a02b49a97c07fcd93d50e8b31640ce2ddb1afeebf605d02R481 # The Pros This PR introduced a new method which will load all releases from databases and all tags on git data into memory. And detect which tags needs to be inserted, which tags need to be updated or deleted. Only tags releases(IsTag=true) which are not included in git data will be deleted, only tags which sha1 changed will be updated. So it will not delete any real releases include drafts. # The Cons The drawback is the memory usage will be higher than before if there are many tags on this repository. This PR defined a special release struct to reduce columns loaded from database to memory.	1 year ago

Author

SHA1

Message

Date

TheFox0x7

33e8e82c4b

Enable tenv and testifylint rules (#32852 )

Enables tenv and testifylint linters
closes: https://github.com/go-gitea/gitea/issues/32842

2 months ago

Lunny Xiao

534917d576

Don't remove all mirror repository's releases when mirroring (#28817 )

Fix #22066

# Purpose

This PR fix the releases will be deleted when mirror repository sync the
tags.

# The problem

In the previous implementation of #19125. All releases record in
databases of one mirror repository will be deleted before sync.
Ref:
https://github.com/go-gitea/gitea/pull/19125/files#diff-2aa04998a791c30e5a02b49a97c07fcd93d50e8b31640ce2ddb1afeebf605d02R481

# The Pros

This PR introduced a new method which will load all releases from
databases and all tags on git data into memory. And detect which tags
needs to be inserted, which tags need to be updated or deleted. Only
tags releases(IsTag=true) which are not included in git data will be
deleted, only tags which sha1 changed will be updated. So it will not
delete any real releases include drafts.

# The Cons

The drawback is the memory usage will be higher than before if there are
many tags on this repository. This PR defined a special release struct
to reduce columns loaded from database to memory.

1 year ago

2 Commits (7069369e0390ab1110a41bcf36a8b7e0ac294226)