Gergely Nagy ade7304eea migrations: Map non-existant external users to Ghost ... When performing migrations, and need to remap external users to local ones, when no local mapping is possible, map the external user to Ghost, rather than the user who initiated the migration. Mapping the external user to the migration initiator has the potential of breaking assumptions elsewhere, like only having one review per pull request per user. Mapping these migrated, locally unavailable users to Ghost makes sure these - often hidden - assumptions do not break. Fixes #3860. Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>		2024-05-28 12:40:11 +02:00
..
3363.md	fix(Dockerfile.rootless): revert to default path for app.ini	2024-04-26 21:30:10 +02:00
3430.md	docs(release-notes): split items in files to avoid conflicts (#3452)	2024-04-26 08:26:33 +00:00
3442.md	docs(release-notes): split items in files to avoid conflicts (#3452)	2024-04-26 08:26:33 +00:00
3729.md	[skip ci] docs(release-notes): 7.0.3	2024-05-22 12:34:50 +02:00
3864.md	add release-notes	2024-05-22 12:59:41 +02:00
3904.md	fix(services): set SendNotificationEmailOnNewUser	2024-05-25 16:27:44 +02:00
3935.md	migrations: Map non-existant external users to Ghost	2024-05-28 12:40:11 +02:00