Merge current v2.10 into v3.0 #10038
Merged
Conversation
This file contains 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
…ion to disable Hub button
mmatur
added
status/2-needs-review
bot/light-review
mmatur
force-pushed
the
feat/merge-back-2.10-into-v3.0
branch
2 times, most recently
from
f8b8ae9
to
1d8713b
Compare
mmatur
force-pushed
the
feat/merge-back-2.10-into-v3.0
branch
from
1d8713b
to
afc6ad5
Compare
ldez
force-pushed
the
feat/merge-back-2.10-into-v3.0
branch
4 times, most recently
from
5d90a56
to
37773ed
Compare
ldez
force-pushed
the
feat/merge-back-2.10-into-v3.0
branch
from
37773ed
to
eb58574
Compare
traefiker
removed
status/3-needs-merge
bot/light-review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
Merge current v2.10 into v3.0.
Motivation
To be in sync.