Rename signup user to new_ user
What does this MR do and why?
Failed pipeline: https://jihulab.com/gitlab-cn/gitlab/-/pipelines/1343339
Failed job: https://jihulab.com/gitlab-cn/gitlab/-/jobs/8342819
Changes from: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/124743/diffs#diff-content-f1b331a515cb8b10c224ce2adb0d9e765db2b36b
diff --git a/ee/app/controllers/trial_registrations_controller.rb b/ee/app/controllers/trial_registrations_controller.rb
index f0c21b78dc6..733e2f140c5 100644
--- a/ee/app/controllers/trial_registrations_controller.rb
+++ b/ee/app/controllers/trial_registrations_controller.rb
@@ -33,6 +33,8 @@ def after_sign_up_path
end
def sign_up_params
+ ensure_correct_params!
+
if params[:user]
params.require(:user).permit(*sign_up_params_attributes)
else
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.