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: support user email verification mechanism #4878
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #4878 +/- ##
============================================
- Coverage 56.81% 56.76% -0.05%
- Complexity 2972 2990 +18
============================================
Files 515 517 +2
Lines 16939 17131 +192
Branches 1274 1283 +9
============================================
+ Hits 9624 9725 +101
- Misses 6773 6862 +89
- Partials 542 544 +2 ☔ View full report in Codecov by Sentry. |
94a8199
to
330ac80
Compare
Signed-off-by: guqing <1484563614@qq.com>
/cc @ruibaby 需要在前端进行适配 |
Working on it |
Signed-off-by: Ryan Wang <i@ryanc.cc>
Signed-off-by: Ryan Wang <i@ryanc.cc>
/retitle feat: support user email verification mechanism Ready for review. 关于 Console 部分的 i18n 我将在后续的 PR 完善,因为分离个人中心之后需要重新整理一下 i18n 文件的结构。 |
/ping @halo-dev/sig-halo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JohnNiang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
/area core
/milestone 2.11.x
What this PR does / why we need it:
新增用户邮箱验证机制
Which issue(s) this PR fixes:
Fixes #4656
Special notes for your reviewer:
Does this PR introduce a user-facing change?