Update devise unlock_instructions mailer text
What does this MR do?
This MR updates the unlock_instructions
email (sent out when a user's account has been locked due to, e.g., 10 failed login attempts) to mention what to do if the user suspects abuse led to the lockout. See https://gitlab.com/gitlab-org/gitlab/-/issues/339154#note_665018660.
Screenshots or Screencasts (strongly suggested)
How to setup and validate locally (strongly suggested)
Visit http://127.0.0.1:3000/rails/mailers/devise_mailer/unlock_instructions to preview the HTML email.
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) - [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
- [-] I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
- [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
-
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Related to #339154
Edited by Luke Duncalfe