Open
Conversation
678aef2 to
b15c577
Compare
b15c577 to
c1e00d7
Compare
c1e00d7 to
ad8f6f6
Compare
ad8f6f6 to
be650c6
Compare
be650c6 to
df92ae3
Compare
df92ae3 to
f0f5b17
Compare
1af387c to
c318898
Compare
c318898 to
aa7e9e9
Compare
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.
What kind of change does this PR introduce?
What is the new behavior?
Turns out the email components package we're using gives us all of this styling for free:
Does this PR introduce a DB Schema Change or Migration?
Git Issues
Closes #4674