Creating a new repo via rest api and 'no_forks' as true does not work as expected.
The forking strategy remains as "Allow only private forks"
Is this affecting the v1.0, the v2.0 API, or both?
It affects V1 when updating repositories as well. I don't know about V2.
Just encountered the same problem on the repository settings page, tried to set the repository to allow no forks, but after saving the changes the option remained unchanged.
Same here. Setting "no forks" on the settings page on the normal web interface does not work. This is not doing much for my trust in bitbucket to keep my repository private.
We're having trouble reproducing this via the ui or the api. Can you confirm you're still seeing this and if so provide any additional details that might help us narrow down the issue?
Since we haven't received a response about this issue in some time, we're closing it. If this is still an issue for anyone, please raise a new issue and we'll look into it.