Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: recovery email #3849

Merged
merged 2 commits into from
May 28, 2024
Merged

feat: recovery email #3849

merged 2 commits into from
May 28, 2024

Conversation

heiytor
Copy link
Contributor

@heiytor heiytor commented May 27, 2024

No description provided.

@heiytor heiytor self-assigned this May 27, 2024
@heiytor heiytor force-pushed the feat/recovery_email branch from e377369 to e844e24 Compare May 27, 2024 12:32
@heiytor heiytor marked this pull request as ready for review May 27, 2024 12:32
@heiytor heiytor requested review from a team as code owners May 27, 2024 12:32
@heiytor heiytor force-pushed the feat/recovery_email branch 11 times, most recently from 1171ff8 to fce1fb9 Compare May 28, 2024 04:37
@luannmoreira luannmoreira requested a review from a team as a code owner May 28, 2024 11:31
heiytor and others added 2 commits May 28, 2024 10:32
Add a `recovery_email` field to the user's model. A recovery email can
be used to recover a user account when they lose access to all other
methods.

Additionaly, we're improving all tests related to `UpdateDataUser`.
This commit add an recovery email field to the Profile Settings, the
recovery_email is meant to add an layer of security to the account
through a new way of validating the users profiles.
@heiytor heiytor force-pushed the feat/recovery_email branch from 9e28773 to 8aa0274 Compare May 28, 2024 13:32
@gustavosbarreto gustavosbarreto merged commit b949237 into master May 28, 2024
8 checks passed
@gustavosbarreto gustavosbarreto deleted the feat/recovery_email branch May 28, 2024 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants