forgejo-federation

Author SHA1 Message Date

Author	SHA1	Message	Date
KN4CK3R	52ef33b931	Remove unused `KeyID`. (#29167 ) `KeyID` is never set. (cherry picked from commit 155269fa586c41a268530c3bb56349e68e6761d7) Conflicts: models/user/email_address.go trivial context conflict	2024-02-16 15:20:52 +01:00
Earl Warren	030cdd6ae2	[GITEA] Allow changing the email address before activation (squash) See https://codeberg.org/forgejo/forgejo/pulls/2300	2024-02-05 16:57:58 +01:00
KN4CK3R	f8b471ace1	Unify user update methods (#28733 ) 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.	2024-02-04 13:29:09 +00:00

KN4CK3R

52ef33b931

Remove unused KeyID. (#29167 )

`KeyID` is never set.

(cherry picked from commit 155269fa586c41a268530c3bb56349e68e6761d7)

Conflicts:
	models/user/email_address.go
	trivial context conflict

2024-02-16 15:20:52 +01:00

Earl Warren

030cdd6ae2

[GITEA] Allow changing the email address before activation (squash)

See https://codeberg.org/forgejo/forgejo/pulls/2300

2024-02-05 16:57:58 +01:00

KN4CK3R

f8b471ace1

Unify user update methods (#28733 )

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.

2024-02-04 13:29:09 +00:00

3 commits