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?
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 email@example.com
For instance say that your username is
scarter and your email address according to LDAP is
Without the checkbox checked, only commits authored by
firstname.lastname@example.org would be allowed.
With the checkbox checked, both
email@example.com would be allowed.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot