-
Notifications
You must be signed in to change notification settings - Fork 72
Updates to allow passing notification communications email to server. #11102
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
base: develop
Are you sure you want to change the base?
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
|
Size Change: +628 B (0%) Total Size: 874 kB
ℹ️ View Unchanged
|
elazzabi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
Hi @rogermattic - I need a design check on this to make sure it makes sense from a Design POV 🙂 are you able to take a look, or let me know who the best person to ask is? Thanks! |

Fixes #5379
Changes proposed in this Pull Request
Adds a new "Notifications" section to the WooPayments settings page, allowing merchants to specify a communications email address for receiving WooPayments-related notifications. This email is preferred when delivering WooPayments related communications.
Testing instructions
Prerequisites
Check out the associated server PR which adds support for this field (ask on Slack 🙂 )
npm run watchto build the JS.Screenshots
npm run changelogto add a changelog file, choosepatchto leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge