Skip to content

fix: update warn user of deletion email#6394

Open
ludtkemorgan wants to merge 1 commit into
mainfrom
1017/warn-user-email
Open

fix: update warn user of deletion email#6394
ludtkemorgan wants to merge 1 commit into
mainfrom
1017/warn-user-email

Conversation

@ludtkemorgan

Copy link
Copy Markdown
Collaborator

This PR addresses #1536

  • Addresses the issue in full
  • Addresses only certain aspects of the issue

Description

Updates the content of the email for warning users of deletion as requested by the Doorway team. Specifically removing reference to the terms of service, linking the privacy policy, and making a word change.

How Can This Be Tested/Reviewed?

Verify the email translations are updated

In order to test that the migration file properly works manual validation is required.

  1. Before pulling down these changes seed the database
  2. Pull down the changes and run yarn db:migration:run
  3. Verify that the database has the new fields and updated language for the accountRemoval field in the translations table

Verify the email looks correct

  1. Seed the database
  2. Create a public user with your email
  3. In the database update the last_login_at and password_updated_at to be way in the past
  4. Set the USER_DELETION_WARN_CRON_STRING value in the .env file to run soon (ideally the next few minutes)
  5. Set the USERS_DAYS_TILL_EXPIRY value in .env file to be a small number (e.g 1)
  6. Wait for the cron job to run and verify the received email looks correct

Author Checklist:

  • Added QA notes to the issue with applicable URLs
  • Reviewed in a desktop view
  • Reviewed in a mobile view
  • Reviewed considering accessibility
  • Added tests covering the changes
  • Made corresponding changes to the documentation
  • Ran yarn generate:client and/or created a migration when required

Review Process:

  • Read and understand the issue
  • Ensure the author has added QA notes
  • Review the code itself from a style point of view
  • Pull the changes down locally and test that the acceptance criteria is met
  • Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates

@netlify

netlify Bot commented Jun 8, 2026

Copy link
Copy Markdown

Deploy Preview for bloom-angelopolis canceled.

Name Link
🔨 Latest commit 1a95fc3
🔍 Latest deploy log https://app.netlify.com/projects/bloom-angelopolis/deploys/6a272c5bb4c84f0008076d04

@netlify

netlify Bot commented Jun 8, 2026

Copy link
Copy Markdown

Deploy Preview for partners-bloom-dev ready!

Name Link
🔨 Latest commit 1a95fc3
🔍 Latest deploy log https://app.netlify.com/projects/partners-bloom-dev/deploys/6a272c5b6a3ce00008362b26
😎 Deploy Preview https://deploy-preview-6394--partners-bloom-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jun 8, 2026

Copy link
Copy Markdown

Deploy Preview for bloom-public-seeds ready!

Name Link
🔨 Latest commit 1a95fc3
🔍 Latest deploy log https://app.netlify.com/projects/bloom-public-seeds/deploys/6a272c5b0b845e00088df58e
😎 Deploy Preview https://deploy-preview-6394--bloom-public-seeds.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jun 8, 2026

Copy link
Copy Markdown

Deploy Preview for bloom-exygy-dev ready!

Name Link
🔨 Latest commit 1a95fc3
🔍 Latest deploy log https://app.netlify.com/projects/bloom-exygy-dev/deploys/6a272c5b5172110008338951
😎 Deploy Preview https://deploy-preview-6394--bloom-exygy-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@ludtkemorgan ludtkemorgan added the 1 review needed Requires 1 more review before ready to merge label Jun 8, 2026

@YazeedLoonat YazeedLoonat left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@YazeedLoonat YazeedLoonat added ready to merge Should be applied when a PR has been reviewed and approved and removed 1 review needed Requires 1 more review before ready to merge labels Jun 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready to merge Should be applied when a PR has been reviewed and approved

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants