Duplicate resource creation during REST API write retries
When integrating external automation with the Bitbucket Server/Data Center REST API, network timeouts during POST requests create uncertainty regarding whether a resource was successfully created on the server before the connection dropped. Because standard write endpoints for entities like pull requests or repositories do not natively support idempotency ke
bitbucket