chore: add current email templates to repo for reference/tracking #355
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
|
@hugomrdias any blockers/feedback to getting these in place so we can start fixing them up and adding features to them in follow-on PRs? |
hugomrdias
approved these changes
Jan 24, 2023
There was a problem hiding this comment.
LGTM
It seems we can use the API to sync these templates https://postmarkapp.com/developer/api/templates-api#get-template maybe we can do that in a follow up PR ?
|
@hugomrdias I don't have write access, could you merge this or tag someone to do so since it's marked as approved? |
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.
This adds copies of the current Postmark
TemplateAlias: 'welcome'content, shared by @travis via:For the purposes of this PR please do not review the actual content! There are some known issues with the current plaintext template that will need to be addressed (xref https://filecoinproject.slack.com/archives/C02BZPRS9HP/p1673986091876469 / #356) and some future enhancements being discussed. But those are examples of things that would be nice to have a commit history for going forward.
The goal of this change is simply to capture the current status quo in the repository, rather than lost/hidden within the Postmark account.