chore: add affiliation and joiningReason to email#4326
Open
jaeyun0503 wants to merge 3 commits intoapache:mainfrom
Open
chore: add affiliation and joiningReason to email#4326jaeyun0503 wants to merge 3 commits intoapache:mainfrom
jaeyun0503 wants to merge 3 commits intoapache:mainfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 changes were proposed in this PR?
This PR adds the fields
affiliationandjoiningReasonto the emails that are automatically sent to admin users to let them have a better overview of the new account requests. Currently when a new user requests access, the emails that are sent to admin users only contain the email information of the new user. We are adding affiliation and joining reason to the email so that admin users can have more information about the new user.Current Email Format
Proposed Email Format
Any related issues, documentation, discussions?
Closes #4325.
How was this PR tested?
Manually Tested.
Was this PR authored or co-authored using generative AI tooling?
No.