@RaynaldM Please approve.
You can understand the problem from emailing thread "Congrats on 20.0.0 release."
This PR is prepared to resolve my mistake I did in #1721 while merging with Rebase option which made a 3 new commits having new hash values, but they don't belong to main branch. It seems GitHub doesn't use fast-forwarding, and creates new commits always. This differs from default Visual Studio settings for git, so VS has more intellectual merging features.
Technically release branch commits are still not delivered to develop. That's why I've created this 2nd PR.
@RaynaldM Please approve. You can understand the problem from emailing thread "Congrats on 20.0.0 release." This PR is prepared to resolve my mistake I did in #1721 while merging with Rebase option which made a 3 new commits having new hash values, but they don't belong to main branch. It seems GitHub doesn't use fast-forwarding, and creates new commits always. This differs from default Visual Studio settings for git, so VS has more intellectual merging features. Technically release branch commits are still not delivered to develop. That's why I've created this 2nd PR.