90875[BUGFIX] Fix type error on empty $be_user_data['realName']
Commit message
Review
-
Code review CR +2 Done
- Stefan Bürk +2
- Garvin Hicking +1
-
Verified V +2 Done
- Stefan Bürk +2
- Garvin Hicking +1
- core-ci +1 CI
Issues 1
Files 1
Review log 1114
-
Mikel Wohlschlegel uploaded patch set 1 10/02/25, 09:59
-
core-ci voted on patch set 1 V -1 10/02/25, 10:07 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85895
-
Mikel Wohlschlegel commented on patch set 1 10/02/25, 10:29
recheck -
core-ci voted on patch set 1 V +1 10/02/25, 10:58 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85895
-
Garvin Hicking updated the commit message in patch set 2
V +110/02/25, 11:21 -
Garvin Hicking commented on patch set 2 CR +1 V +1 10/02/25, 11:21
Thanks, good catch! -
core-ci voted on patch set 2 V +1 10/02/25, 11:31 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85910
-
Garvin Hicking commented on patch set 2 10/02/25, 11:34
Reply
Done -
Stefan Bürk voted on patch set 2 CR +2 V +2 10/02/25, 21:01
-
Stefan Bürk commented on patch set 2 CR 0 V 0 10/02/25, 21:08
Usually patches are provided for the newes branch fist (main) and we backport things and voting happens on the main change. That means moving a change first to main. Created now main and 13.4 as "up-ports" and voting should be done on https://review.typo3.org/c/Packages/TYPO3.CMS/+/90885 to keep the chain how it should be and looking later into the chain does not confuse peopls seeing only one core merger +2 on a main-branch change not expected. @garvin@hick.ing please revote/check main branch change. -
Stefan Bürk wrote 10/02/25, 21:31
Removed reviewer Stefan Bürk. -
Stefan Bürk voted on patch set 2 CR +2 V +2 10/03/25, 07:43
-
Stefan Bürk merged patch set 3 10/03/25, 07:43
-
Stefan Bürk commented on patch set 3 10/03/25, 07:44
Reply
Done