Skip to content

Merge branch 'master' into release/bugpatch#2327

Merged
tomgreenfield merged 72 commits intorelease/bugpatchfrom
resolveConflicts
May 10, 2019
Merged

Merge branch 'master' into release/bugpatch#2327
tomgreenfield merged 72 commits intorelease/bugpatchfrom
resolveConflicts

Conversation

@tomgreenfield
Copy link
Copy Markdown
Contributor

  • Resolve conflicts
  • Ensure relative URLs in theme editor

@canstudios-nicolaw
Copy link
Copy Markdown
Contributor

Thanks for this @tomgreenfield. I've switched to this branch locally and given it a brief test. I think it's best if I 👀 approve this. Before we release I'll put the bugpatch branch on a testing server here and ask QA to give it a smoke test.

Copy link
Copy Markdown
Contributor

@canstudios-nicolaw canstudios-nicolaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👀

@tomgreenfield
Copy link
Copy Markdown
Contributor Author

Cheers, I'll go ahead and merge this now and get the full complement of +1s for the PR into master.

@tomgreenfield tomgreenfield merged commit 35c468a into release/bugpatch May 10, 2019
@tomgreenfield tomgreenfield deleted the resolveConflicts branch May 10, 2019 13:31
@canstudios-nicolaw
Copy link
Copy Markdown
Contributor

canstudios-nicolaw commented May 10, 2019

@tomgreenfield It's not clear to me if we are waiting for a potential fix for the issue mentioned on #2261 ?

(Before we do the release)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants