[TASK] Use assignMultiple() where appropriate

[brotkrueml]

Releases: main, 12.4

[linawolf]

What is the advantage in doing this? Isn't chaining just as valid? Is this an official recommendation?

[garvinhicking]

(Lina: It's less op-calls to perform, and IMO has less redundancy and is clearer to read)

[brotkrueml]

Yup, my intention was better readability.

[github-actions]

The backport to 12.4 failed:

The process '/usr/bin/git' failed with exit code 1

stderr

error: could not apply 7f74d5f... [TASK] Use assignMultiple() where appropriate
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

stdout

Auto-merging Classes/Controller/BlogController.php
CONFLICT (content): Merge conflict in Classes/Controller/BlogController.php
Auto-merging Classes/Controller/PostController.php
CONFLICT (content): Merge conflict in Classes/Controller/PostController.php

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-12.4 12.4
# Navigate to the new working tree
cd .worktrees/backport-12.4
# Create a new branch
git switch --create backport-85-to-12.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 7f74d5f175d0cd6c262e2f00bc7fac2a89bc8572
# Push it to GitHub
git push --set-upstream origin backport-85-to-12.4
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-12.4

Then, create a pull request where the base branch is 12.4 and the compare/head branch is backport-85-to-12.4.