Send copy of call for speakers email to the speaker itself#1053
Merged
outdoor2kode merged 2 commits intoWordPress:productionfrom Apr 29, 2024
Merged
Send copy of call for speakers email to the speaker itself#1053outdoor2kode merged 2 commits intoWordPress:productionfrom
outdoor2kode merged 2 commits intoWordPress:productionfrom
Conversation
Collaborator
Author
|
The linting errors are due to action/filter list styling that has been the preferred way in WordCamp.org but for some reason, phpcs decided to nag about it... |
This was referenced May 30, 2025
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
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.

When the speaker submits a talk to WordCamp, send a "receipt" of that to the speaker. It will help people keep track of what talks they’ve submitted to WordCamps, and when.
Instead of sending out separate emails and handling logic for that, I decided to just modify the email that goes out in any case. This helps to keep the code a tad cleaner, but has also the added benefit of organisers being able to reply to that email and continue the discussion with the speaker on a thread that has all of the submitted information. In addition, the same code can be extended for sponsor and volunteer applications easily.
Fixes #376
Props @melchoyce
Screenshots
How to test the changes in this Pull Request: