Conversation
Release 20.0.0
Release 20.0 codenamed as "Polish Apple"
raman-m
added
release
Member
Author
|
@RaynaldM Hey Ray! |
RaynaldM
approved these changes
Oct 11, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@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.