I'm seeing unknown users checking in code to PRIVATE repositories. I found out who they are by reviewing it with my teams, but the system should automatically disallow this from happening. If a repository is PRIVATE, it should ONLY allow access to the people that have permissions to access it. That includes doing any management on it.
The issue here is that people who currently have access to this repository are committing with incorrect e-mail aliases. See: https://confluence.atlassian.com/bitbucket/set-your-username-for-bitbucket-cloud-actions-272597445.html
If they have an unknown e-mail set in their .gitconfig file, then it will show up as "Unknown" under Bitbucket, as it does not match their primary e-mail on Bitbucket. Once they fix this, their subsequent commits will show up under their correct user account.
They can also set their Email alias under *Bitbucket Settings*, so it can attribute to incorrect commits to the correct user.
There is no way to disallow this from happening, but I've created a feature request: https://bitbucket.org/site/master/issues/14663/create-flag-to-prevent-unknown-committers
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