Don't send email when importing members using DirectTransfer
What does this MR do and why?
Don't send email when importing members using DirectTransfer
When performing a Direct Transfer migration user gets email
notification for each project/group they've been added to,
which can result in many emails. Update MembersPipeline and
mark each member with importing
flag to skip
emailing callback.
Member#post_create_hook
after create callback is responsible for sending the email. So adding importing = true
during member creation should skip all callbacks that are marked for exclusion when importing. This was previously done for file-based Import/Export, so having emails in Direct Transfer was an oversight.
Changelog: other
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
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.