Enforce Push Author Stash Hook

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?


2 answers

1 votes


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 is configured in the user directory (could be the LDAP directory)
  • 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!

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

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&nbsp...

636 views 0 4
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot