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.
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!
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