403/"Repository currently not available." after forking a repository.

[Alex C.]

Hi @ all,

i am using Bitbucket Cloud and i am forking a Repository through Rest-API v1

This is working very well, but if i try to make changes to this new Repository immediately after the fork, the Endpoint says "Repository currently not available".

Granting write permission to a specific user is ok, but registering a Webhook or trying to commit a single Textfile immediately after forking gives me a "Repository currently not available."

If i try the same steps after a while its working, but to complete my task i must be able to do the after-fork-operations immediately.

Any change to prevent this?

Thanks in advance.

[Ana Retamal]

Hi Alex! Forking a repo is not an immediate operation, that's why when you try to access it right after you sent the you'll get the message "Repository currently not available", the repo hasn't been created yet.

You can use the API every few seconds to find out if the repo has already been created and once you get a successful response you can continue with the rest of your operations.

Hope that helps!

Ana