Hello,
I'm trying to figure out the exact undocumented private commit email format for my account (i.e. the one automatically assigned) so the commits show a proper profile picture and are signed/verified. https://www.google.com/search?q=%22users.noreply.bitbucket%22&udm=14 has 4 results only and none are helpful.
Hello and welcome to the Community @46009361
I would be a little careful with the noreply idea here.
I could not find any current Atlassian documentation for a Bitbucket Cloud private commit email format that is meant to be used the way GitHub’s is. What Atlassian does document is using your primary email or a confirmed email alias so Bitbucket can map the commit back to your account correctly.
For the verified part, I would treat that as a separate topic. Bitbucket Cloud supports GPG and SSH commit signing, and Atlassian’s docs note that verification can fail because of an email mismatch.
The safer Way would be to use a confirmed email alias for author/avatar mapping, and GPG or SSH signing for verified commits. Unless Atlassian confirms a noreply format directly, I would not rely on an undocumented pattern here.
This Feature request still seems not implemented:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.