Our repo is private and team with access.
I and my colleagues is in team.
We sometimes upload the images when PR but has some problems.
The question is my colleagues couldn't look image after I uploaded .
I also failed to look image colleagues uploaded.
The messages when I openned is "Access denied"
Why we can't look others images?
We've had this problem as well. As far as I can tell it's caused by inconsistencies with how how Bitbucket resolves permissions.
As per https://blog.bitbucket.org/2014/02/12/new-direct-image-uploads-for-bitbucket/ images uploaded have the same permission as the repository.
However, in the case of a PR from a fork to a main repo, there are a couple repositories with potentially different permissions in play. What we've found is that when initially creating the PR, the images have the permissions of JUST the source repository. Once the PR has been created though, adding images in comments or editing the description to include an image pulls permissions from both source and destination repo.
In practice you can resolve the above issue by either:
• Inviting your co-workers as collaborators on your private fork, Or;
• Don't add images until after you've initially created the PR
Hopefully Atlassian will fix the underlying issue at some point and just make sure images have the correct permissions from both source and destination repos during creation.
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