chore: merge master branch to develop#2396
Merged
jasonbahl merged 9 commits intowp-graphql:developfrom Jun 3, 2022
Merged
Conversation
Release/v1.8.2
68c056f to
8e94bca
Compare
|
Code Climate has analyzed commit 8e94bca and detected 0 issues on this pull request. View more on Code Climate. |
Collaborator
Author
|
Note: had to explicitly set |
2 tasks
jasonbahl
approved these changes
Jun 3, 2022
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
3 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.
What does this implement/fix? Explain your changes.
v1.8.2 was merged directly with the
masterbranch, instead of the usualrelease/branch->develop->master.This PR pulls those changes back onto the
developbranch.Does this close any currently open issues?
…
Any relevant logs, error output, GraphiQL screenshots, etc?
(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)
Any other comments?
Might make sense to set some branch protection rules to enforce the following rules, instead of just as a note in the PULL_REQUEST_TEMPLATE
developcan be merged with master.develop.Ref:
Where has this been tested?
Operating System: N/A
WordPress Version: N/A