fix(router): skipLocationChange with named outlets (patch fix) - #28301

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

I see that you just added the PR action: merge label, but the following checks are still failing:
     status "cla/google" is failing
     missing required labels: cla: yes
     status "ci/circleci: test_aio" is pending
     status "ci/circleci: build-packages-dist" is pending
     status "ci/circleci: test" is pending
     status "ci/circleci: legacy-unit-tests-saucelabs" is pending
     status "ci/circleci: test_ivy_aot" is pending
     status "ci/circleci: legacy-unit-tests-local" is pending
     status "ci/circleci: aio_preview" is pending
     status "ci/circleci: lint" is pending
     status "ci/angular: size" is pending
     1 pending code review

If you want your PR to be merged, it has to pass all the CI checks.

If you can't get the PR to a green state due to flakes or broken master, please try rebasing to master and/or restarting the CI job. If that fails and you believe that the issue is not due to your change, please contact the caretaker and ask for help.

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

Merged in 32737a6.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}