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
*	Enable testifylint rules (#34075)	TheFox0x7	2025-03-31	1	-6/+6
\| \| \| \|	enable testifylint rules disabled in: https://github.com/go-gitea/gitea/pull/34054
*	Move ParseBool to optional (#33979)	Lunny Xiao	2025-03-24	2	-0/+24
\|
*	Resolve lint for unused parameter and unnecessary type arguments (#30750)	Chongyi Zheng	2024-04-29	1	-1/+1
\| \| \| \| \| \| \| \| \| \|	Resolve all cases for `unused parameter` and `unnecessary type arguments` Related: #30729 --------- Co-authored-by: Giteabot <teabot@gitea.io>
*	Add `interface{}` to `any` replacement to `make fmt`, exclude `*.pb.go` (#30461)	silverwind	2024-04-13	1	-1/+1
\| \| \| \| \| \| \|	Since https://github.com/go-gitea/gitea/pull/25686, a few `interface{}` have sneaked into the codebase. Add this replacement to `make fmt` to prevent this from happening again. Ideally a linter would do this, but I haven't found any suitable.
*	migrate some more "OptionalBool" to "Option[bool]" (#29479)	6543	2024-02-29	1	-0/+10
\| \| \| \| \| \| \| \|	just some refactoring bits towards replacing util.OptionalBool with optional.Option[bool] --------- Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
*	Make optional.Option[T] type serializable (#29282)	6543	2024-02-23	3	-10/+248
\| \| \| \| \| \| \|	make the generic `Option` type de-/serializable for json and yaml --------- Co-authored-by: KN4CK3R <admin@oldschoolhack.me>
*	Start to migrate from `util.OptionalBool` to `optional.Option[bool]` (#29329)	6543	2024-02-23	1	-3/+2
\| \| \|	just create transition helper and migrate two structs
*	Unify user update methods (#28733)	KN4CK3R	2024-02-04	2	-0/+93
	Fixes #28660 Fixes an admin api bug related to `user.LoginSource` Fixed `/user/emails` response not identical to GitHub api This PR unifies the user update methods. The goal is to keep the logic only at one place (having audit logs in mind). For example, do the password checks only in one method not everywhere a password is updated. After that PR is merged, the user creation should be next.