This seems like a big hole in how the review approval process works.
we've seen people accidently clone the main repo instead of their fork. Their pushes go straight in, no review.
how do we prevent this?
Sorry, for topic I didn't see git/stash anywhere. Don't know what topic to add.
to the guy who answered...I can't reply to your reply...
can you be more specific?
we already require that PRs have a reviewer approve it.
but that doesn't stop someone from going in the back door.
Where do you set such permissions? I don't see anything in the GUI
In the branch permissions, you can add a permission to prevent changes without a pull request. This would force users to create a pull request from the fork instead of check in directly to the main repo.
PS: For the topic, select bitbucket-server.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot