This is exactly what #23229 is. That PR is not yet merged to 4.0.

If a change has already been made on staging (3.x), it does not need a separate pull request for 4.0. It will eventually merge forward as the backlog clears out.

Ok then I'll close this

@mbabker just had one question
Since naming convention for files have changed in J4
In J(3.x) we had view.html.phpwhereas in J4 we have HtmlView.php
Will that not make merging difficult?

That is why there is a backlog. But it's a waste of resources to do things twice

Since naming convention for files have changed in J4
In J(3.x) we had view.html.phpwhereas in J4 we have HtmlView.php
Will that not make merging difficult?

Depends on a lot of variables. If files were all moved with git's move command, its history usually does a pretty good job of saying "this file has been moved, so apply this segment of the diff to the new location instead". When things get too far diverged that's when you start running into problems with git not being able to sanely follow your renames. I've redone the folder structure on an application just as large as Joomla and thanks to carefully moving files when I needed to merge changes for the live production system into the in-progress refactoring I usually only ran into problems where other changes had been made (such as splitting a large monolithic config resource into smaller files).

ok got it
I'm closing this PR