Merge 5.3.15 into 5.4.x #3227
Closed
Merge 5.3.15 into 5.4.x #3227
Conversation
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
|
The async regen has found a file to delete, so I have to amend my merge it seems. |
|
Well that is odd, double async regen, the second one undoing what the first has done... I guess I will still push directly the merge commit as it is. A local async regen does not change any files. |
bahusoid
approved these changes
Jan 30, 2023
fredericDelaporte
force-pushed
the
5.4.x
branch
from
2499393 to
fc8d55c
Compare
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.
I intend to push directly the merge commit, if this PR is validated.