New/unknown sign-in email email styling
What does this MR do?
Relates to #218443 (closed) (and sort of #215652)
Makes the unknown/new sign in email look more legitimate and clarifies what's happened.
Although the unknown sign in feature has been mostly working as intended, we have had some user feedback. The 'plain text' nature of the email was suspicious to some and they thought it was phishing. Others were confused by where they had actually signed in since the GitLab hostname (gitlab.com) wasn't especially prominent.
This change attempts to unify the email with an established email styling. We currently use this format for the pipeline and merge request approval emails. I'm no frontend developer or UX designer so I am sure this needs some fine tuning but it's something to start from.
Screenshots
Modeled from
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team