Cleaned up duplicate variable assignments in the same line

[bgorski]

Description (*)

Re-apply changes from #28085
This is a simple cleanup of two assignments to the same variable occurring in the same line.
Created by using the following regex:
($.*) = \1 = (with space before to exclude things like self::$loader = $loader = new \Composer\Autoload\ClassLoader(); and with space after to make sure it's an assignment and not anything else like ===)
And replacing with:
$1 = (also with space before and after to keep the formatting right)

Related Pull Requests

Fixed Issues (if relevant)

Manual testing scenarios (*)

none required

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

Resolved issues:

1. resolves [Issue] Cleaned up duplicate variable assignments in the same line #30133: Cleaned up duplicate variable assignments in the same line

[m2-assistant]

Hi @bgorski. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[bgorski]

@magento run all tests

[ihor-sviziev]

@magento run all tests

[ihor-sviziev]

Hi @bgorski,
Could you fix the failing static tests for changed files?

Thank you!

[bgorski]

@magento run Static Tests

[bgorski]

@magento run Static Tests

[bgorski]

@magento run Static Tests

[ihor-sviziev]

@magento run all tests

[sidolov]

@magento create issue

[magento-engcom-team]

Hi @ihor-sviziev, thank you for the review.
ENGCOM-8242 has been created to process this Pull Request

[m2-assistant]

Hi @bgorski, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.