Skip to content

fix: handle AppMember.email conflicts and make user connection optional

Before assigning a reviewer go through the following checklist, and make sure to test your changes manually (if possible).

  • Make sure to read the CONTRIBUTING.md for best practices and guidelines.
  • Make sure to put the merge request on draft: if it's not ready.
  • If this merge requests closes an issue, make sure the merge request description contains, closes #the-issue-number.
  • If this merge request only relates to an issue, refer to the issue with refs #the-issue-number.
  • If there is no related issue, consider adding a description and add labels accordingly.
  • If this is a bug fix, consider adding regression tests.
  • If this is blocked by another merge request, make sure to make it depend.

TIP: Use ~ in the checklist item (like this - [~]) to strike it out if it's not applicable.

Has to be reviewed after !3691 (closed)

Closes #1481 (closed), #1253 (closed), #1308 (closed)

Edited by Vasil Velikov

Merge request reports

Loading