Fix/admin 2614 user invitation email uppercase #2624
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KoWeiJAC
requested review from
tomlovesgithub,
HalcyonJAC,
drieJAC and
nickaddy
|
Visit the preview URL for this PR (updated for commit 282a0a8): https://jac-admin-develop--pr2624-fix-admin-2614-user-jhi8ff7t.web.app (expires Sat, 28 Dec 2024 10:38:26 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 4e92cf51659207b0ae3509dc5c40edde50edfec0 |
drieJAC
approved these changes
Nov 27, 2024
HalcyonJAC
approved these changes
Nov 27, 2024
nickaddy
approved these changes
Nov 27, 2024
tomlovesgithub
approved these changes
Nov 27, 2024
HalcyonJAC
force-pushed
the
fix/admin-2614-user-invitation-email-uppercase
branch
from
4d2cb6a to
282a0a8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What's included?
Closes #2614
Who should test?
✅ Product owner
✅ Developers
✅ UTG
How to test?
Screen.Recording.2024-11-27.at.14.47.03.mov
Risk - how likely is this to impact other areas?
🟢 No risk - this is a self-contained piece of work
Additional context
Include screen grabs, video demo, notes etc.
Related permissions
Have permissions been considered for this functionality?
PREVIEW:DEVELOP
can be OFF, DEVELOP or STAGING