What special case does checking the "Allow alternate email (<username>@)" check box allow for?
The obvious assumption is that it allows an alternate email but wouldn't that directly oppose the default check "Require matching email address (required)" which cannot be turned off?
Thanks,
Seth
Seth,
The logic appears to be a bit more subtle. When the 'Allow alternate email' check box is checked, the hook will allow two email addresses:
The one that matches username@domain.configured.in.user.directory
For instance say that your username is scarter
and your email address according to LDAP is seth.carter@company.com
.
Without the checkbox checked, only commits authored by seth.carter@company.com
would be allowed.
With the checkbox checked, both seth.carter@company.com
and scarter@company.com
would be allowed.
Thanks Michael, while it isn't what I wanted it to be it does explain what it actually does!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the discussion on interview best practices and common pitfalls. Share your experiences and learn from others in the Atlassian Community.
Share you experiences!Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.