Member Resolver not Resolving by Nick/User after Update #2

Closed
opened 2020-04-15 10:45:53 -04:00 by matthew · 2 comments
matthew commented 2020-04-15 10:45:53 -04:00 (Migrated from gitlab.libraryofcode.org)

After MR !2 it appears that the member resolver isn't resolving by just plain nick/username anymore.
image

After MR !2 it appears that the member resolver isn't resolving by just plain nick/username anymore. ![image](/uploads/80fb36e228fd5fa8efca86eae6d79dd0/image.png)
Bsian commented 2020-04-15 11:12:40 -04:00 (Migrated from gitlab.libraryofcode.org)

closed via commit b4ff1ce805

closed via commit b4ff1ce80531f5f52a288b6b2f8fae3bff55d544
Bsian commented 2020-04-16 11:25:29 -04:00 (Migrated from gitlab.libraryofcode.org)
mentioned in commit DedShotTM/communityrelations@b4ff1ce80531f5f52a288b6b2f8fae3bff55d544
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: engineering/community-relations#2
There is no content yet.