emcconville / wand Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix regression on issue #320 #435
Closed
mplitnikas-iti
wants to merge
30
commits into
emcconville:0.5-maintenance
from
mplitnikas-iti:master
Closed
fix regression on issue #320 #435
mplitnikas-iti
wants to merge
30
commits into
emcconville:0.5-maintenance
from
mplitnikas-iti:master
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
Thanks for the effort, but it looks like this is the sum of the next release (still in development) being merged down to the maintenance branch. This gets handled automatically by the release cycle, and doesn't require a merge-request. |
ah, that makes sense. Sorry about the giant merge request |
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.
Looks like the relevant changes got left behind in a merge request or similar, so I cherry-picked it.